Displays for a medical device

ABSTRACT

Embodiments described herein relate to an analyte monitoring device having a user interface with a display and a plurality of actuators. The display is configured to render a plurality of display screens, including a home screen and an alert screen. The home screen is divided into a plurality of simultaneously displayed panels, with a first panel displays a rate of change of continuously monitored analyte levels in interstitial fluid, a second panel simultaneously displays a current analyte level and an analyte trend indicator, and a third panel displays status information of a plurality of components of the device. When an alarm condition is detected, the display renders the alert screen in place of the home screen, the alert screen displaying information corresponding to the detected alarm condition. Furthermore, the actuators are configured to affect further output of the analyte monitoring device corresponding to the detected condition.

RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 13/970,556 filed Aug. 19, 2013, now U.S. Pat. No. 8,816,862,which is a continuation of U.S. patent application Ser. No. 12/871,901filed Aug. 30, 2010, now U.S. Pat. No. 8,514,086, which claims to thebenefit of U.S. Provisional Patent Application No. 61/238,672, entitled“Analyte Monitoring System Having a User Interface”, filed on Aug. 31,2009, U.S. Provisional Patent Application No. 61/238,657, entitled“Medical Device Having Illumination Assembly”, filed on Aug. 31, 2009,U.S. Provisional Patent Application No. 61/247,541 entitled “Alarms ForA Medical Device”, filed on Sep. 30, 2009 and U.S. Provisional PatentApplication No. 61/297,625, entitled “Displays for a Medical Device”,filed on Jan. 22, 2010, the disclosures of each of which areincorporated herein by reference in their entirety for all purposes.

BACKGROUND

Diabetes mellitus is an incurable chronic disease in which the body doesnot produce or properly utilize insulin. Insulin is a hormone producedby the pancreas that regulates blood glucose. In particular, when bloodglucose levels rise, e.g., after a meal, insulin lowers the bloodglucose levels by facilitating blood glucose to move from the blood intothe body cells. Thus, when the pancreas does not produce sufficientinsulin, (a condition known as Type 1 Diabetes) or does not properlyutilize insulin (a condition known as Type 2 Diabetes), the bloodglucose remains in the blood resulting in hyperglycemia or abnormallyhigh blood sugar levels.

People suffering from diabetes often experience long-term complications.Some of these complications include blindness, kidney failure, and nervedamage. Additionally, diabetes is a factor in acceleratingcardiovascular diseases such as atherosclerosis (hardening of thearteries), which often leads to stroke, coronary heart disease, andother diseases which can be life threatening.

The severity of the complications caused by both persistent high glucoselevels and blood glucose level fluctuations has provided the impetus todevelop diabetes management systems and treatment plans. In this regard,diabetes management generally includes multiple daily testing of bloodglucose levels by applying blood samples to test strips and analyzingthe blood sample using a blood glucose meter. More recently, diabetesmanagement has included continuous glucose monitoring systems. Glucosemonitoring systems have the capability to continuously monitor a user'sblood glucose fluctuations over a period of time and display the resultsto a user.

In such systems, it would be desirable to have a display and/or a userinterface capable of robust, comprehensive information presentation,analysis, processing, user manipulation and/or usability featuresincluding, for example, programmable alarms and alerts, comprehensivevisual, audible and/or vibratory output for assisting in diabetesmanagement and improving glycemic control.

SUMMARY

Embodiments described herein relate to an analyte monitoring devicehaving a user interface with a display and a plurality of actuators. Thedisplay is configured to output a plurality of display screens,including at least a home screen and an alert screen. The home screen isdivided into a plurality of simultaneously displayed panels, with afirst panel of the plurality of panels configured to display a rate ofchange of continuously monitored analyte levels in interstitial fluid, asecond panel configured to simultaneously display a current analytelevel and an analyte trend indicator, and a third panel configured todisplay status information of a plurality of components of the analytemonitoring device. When an alert condition is detected, an alert screenis output on the display in place of the home screen. The alert screendisplays information corresponding to the detected alert condition.Furthermore, the plurality of actuators are configured to affect furtheroutput of the analyte monitoring device corresponding to the detectedalert condition.

These and other objects, features and advantages of the presentdisclosure will become more fully apparent from the following detaileddescription of the embodiments, the appended claims and the accompanyingdrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of a data monitoring and managementsystem for practicing one or more embodiments of the present disclosure;

FIGS. 2A-2C illustrate an exemplary analyte monitoring device accordingto embodiments of the present disclosure;

FIG. 2D illustrates an illumination assembly for the exemplary analytemonitoring device according to embodiments of the present disclosure;

FIGS. 3A-3C illustrate various home screen displays of a user interfaceof the analyte monitoring device according to embodiments of the presentdisclosure;

FIGS. 3D-3J illustrate exemplary trend indicator displays that may beused in conjunction with the home screen displays of FIGS. 3A-3Caccording to embodiments of the present disclosure;

FIGS. 4A-4F illustrate display screens showing timeline graphs accordingto embodiments of the present disclosure;

FIG. 5A illustrates a method for retrospectively evaluating a series ofreceived glucose values to detect an alert condition by comparing thereceived glucose values to a trigger window according to embodiments ofthe present disclosure;

FIG. 5B illustrates a graph in which a trigger window is defined withrespect to a current glucose data value according to embodiments of thepresent disclosure;

FIG. 5C illustrates a method for retrospectively evaluating a series ofreceived glucose data values to detect an alert condition by comparingthe received glucose data values to a trigger window according toembodiments of the present disclosure;

FIG. 5D is a graph illustrating a detected rise in glucose levels thatis currently occurring according to embodiments of the presentdisclosure;

FIG. 5E illustrates a method for detecting an alert condition in aglucose monitoring system by retrospectively comparing historicalglucose data values to each of the other historical data values withrespect to a trigger window according to embodiments of the presentdisclosure;

FIG. 5F illustrates a graph for retrospectively comparing a second mostrecently received glucose data value to historical glucose data valueswith respect to a trigger window according to embodiments of the presentdisclosure;

FIG. 5G illustrates a graph in which a trigger window is defined withrespect to a current glucose data value and a previously receivedglucose data value according to embodiments of the present disclosure;

FIG. 5H is a graph illustrating episode detection in which all glucosedata values associated with the episode fall within an outer limit rangeaccording to embodiments of the present disclosure;

FIG. 6 illustrates an exemplary menu screen according to embodiments ofthe present disclosure;

FIG. 7 illustrates an exemplary sensor menu screen according toembodiments of the present disclosure;

FIG. 8 illustrates an exemplary alarm settings menu screen according toembodiments of the present disclosure;

FIG. 9 illustrates an exemplary mute alarms menu screen according toembodiments of the present disclosure;

FIG. 10 illustrates an exemplary glucose alarm threshold display screenaccording to embodiments of the present disclosure;

FIG. 11 illustrates an exemplary alarm tones display screen according toembodiments of the present disclosure;

FIG. 12A illustrates an exemplary snooze setup display screen accordingto embodiments of the present disclosure;

FIG. 12B illustrates an exemplary charging setup display screenaccording to embodiments of the present disclosure;

FIGS. 13-16 illustrate a set of exemplary set alarm profile displayscreens according to embodiments of the present disclosure;

FIGS. 17A-17C illustrate exemplary Continuous Glucose Monitoring (CGM)statistic display screens according to embodiments of the presentdisclosure;

FIG. 18 illustrates an exemplary status display screen according toembodiments of the present disclosure;

FIGS. 19-21 illustrate exemplary alert screens according to embodimentsof the present disclosure;

FIG. 22 is a flow chart illustrating a method for displaying sensor dataaccording to embodiments of the present disclosure;

FIG. 23 illustrates a flow chart for outputting an alert based on adetected alert condition according to embodiments of the presentdisclosure;

FIG. 24A illustrates a flow chart for outputting display screens basedon a detected alert condition according to embodiments of the presentdisclosure;

FIGS. 24B-24C illustrate additional exemplary alert screens according toembodiments of the present disclosure;

FIGS. 25A-25G describe various embodiments relating to the suppressionof alarms based on alert conditions according to embodiments of thepresent disclosure; and

FIG. 26 illustrates an exemplary flow of a plurality of user interfacescreens according to embodiments of the present disclosure.

DETAILED DESCRIPTION

Before the present disclosure is described in detail, it is to beunderstood that this disclosure is not limited to particular embodimentsdescribed, as such may, of course, vary. It is also to be understoodthat the terminology used herein is for the purpose of describingparticular embodiments only, and is not intended to be limiting, sincethe scope of the present disclosure will be limited only by the appendedclaims.

Where a range of values is provided, it is understood that eachintervening value, to the tenth of the unit of the lower limit unlessthe context clearly dictates otherwise, between the upper and lowerlimit of that range and any other stated or intervening value in thatstated range, is encompassed within the disclosure. The upper and lowerlimits of these smaller ranges may independently be included in thesmaller ranges is also encompassed within the disclosure, subject to anyspecifically excluded limit in the stated range. Where the stated rangeincludes one or both of the limits, ranges excluding either or both ofthose included limits are also included in the disclosure.

Unless defined otherwise, all technical and scientific terms used hereinhave the same meaning as commonly understood by one of ordinary skill inthe art to which this disclosure belongs. Although any methods andmaterials similar or equivalent to those described herein can also beused in the practice or testing of the present disclosure, the preferredmethods and materials are now described. All publications mentionedherein are incorporated herein by reference to disclose and describe themethods and/or materials in connection with which the publications arecited.

It must be noted that as used herein and in the appended claims, thesingular forms “a”, “an”, and “the” include plural referents unless thecontext clearly dictates otherwise.

The publications discussed herein are provided solely for theirdisclosure prior to the filing date of the present application. Nothingherein is to be construed as an admission that the present disclosure isnot entitled to antedate such publication by virtue of prior disclosure.Further, the dates of publication provided may be different from theactual publication dates which may need to be independently confirmed.

As will be apparent to those of skill in the art upon reading thisdisclosure, each of the individual embodiments described and illustratedherein has discrete components and features which may be readilyseparated from or combined with the features of any of the other severalembodiments without departing from the scope or spirit of the presentdisclosure.

The figures shown herein are not necessarily drawn to scale, with somecomponents and features being exaggerated for clarity.

Various exemplary embodiments of the analyte monitoring system andmethods of the disclosure are described in further detail below.Although the disclosure is described primarily with respect to a glucosemonitoring system, each aspect of the disclosure is not intended to belimited to the particular embodiment so described. Accordingly, it is tobe understood that such description should not be construed to limit thescope of the disclosure, and it is to be understood that the analytemonitoring system can be configured to monitor a variety of analytes, asdescribed below.

Embodiments described below relate to an analyte monitoring devicehaving a user interface with a display and a plurality of actuators. Thedisplay is configured to output a plurality of display screens,including at least a home screen and an alert screen. In certainembodiments, the home screen is divided into a plurality ofsimultaneously displayed panels, with a first panel of the plurality ofpanels configured to display a rate of change of continuously monitoredanalyte levels in interstitial fluid, a second panel configured tosimultaneously display a current analyte level and an analyte trendindicator, and a third panel configured to display status information ofa plurality of components of the analyte monitoring device. In certainembodiments, when an alert condition is detected, an alert screen isoutput on the display in place of the home screen. The alert screendisplays information corresponding to the detected alert condition. Incertain embodiments, the plurality of actuators are configured to affectfurther output of the analyte monitoring device corresponding to thedetected alert condition.

FIG. 1 illustrates a data monitoring and management system such as, forexample, an analyte (e.g., glucose) monitoring system 100 in accordancewith embodiments of the present disclosure. The analyte monitoringsystem 100 includes a sensor 101, a transmitter unit 102 coupleable tothe sensor 101, and a primary receiver unit 104 which is configured tocommunicate with the transmitter unit 102 via a bi-directionalcommunication link 103. The primary receiver unit 104 may be furtherconfigured to transmit data to a data processing terminal 105 forevaluating the data received by the primary receiver unit 104. Moreover,the data processing terminal 105 in one embodiment may be configured toreceive data directly from the transmitter unit 102 via a communicationlink which may optionally be configured for bi-directionalcommunication. Accordingly, transmitter unit 102 and/or receiver unit104 may include a transceiver.

Also shown in FIG. 1 is an optional secondary receiver unit 106 which isoperatively coupled to the communication link and configured to receivedata transmitted from the transmitter unit 102. Moreover, as shown inthe Figure, the secondary receiver unit 106 is configured to communicatewith the primary receiver unit 104 as well as the data processingterminal 105. The secondary receiver unit 106 may be configured forbidirectional wireless communication with each or one of the primaryreceiver unit 104 and the data processing terminal 105. In oneembodiment of the present disclosure, the secondary receiver unit 106may be configured to include a limited number of functions and featuresas compared with the primary receiver unit 104. As such, the secondaryreceiver unit 106 may be configured substantially in a smaller compacthousing or embodied in a device such as a wrist watch, pager, mobilephone, PDA, for example. Alternatively, the secondary receiver unit 106may be configured with the same or substantially similar functionalityas the primary receiver unit 104. The primary receiver unit 104 and/orsecondary receiver unit 106 may be configured to be used in conjunctionwith a docking cradle unit for one or more of, for example, thefollowing or other functions: placement by bedside, re-charging, datamanagement, night time monitoring, and/or bidirectional communication.

In one aspect analyte monitoring system 100 may include two or moresensors, each configured to communicate with transmitter unit 102.Furthermore, while only one transmitter unit 102 and data processingterminal 105 are shown in the embodiment of the analyte monitoringsystem 100 illustrated in FIG. 1, it will be appreciated by one ofordinary skill in the art that the analyte monitoring system 100 mayinclude one or more sensors, multiple transmitter units 102,communication links 103, and data processing terminals 105. Moreover,within the scope of the present disclosure, the analyte monitoringsystem 100 may be a continuous monitoring system, or semi-continuous, ora discrete monitoring system. In a multi-component environment, incertain embodiments, each device may be configured to be uniquelyidentified by each of the other devices in the system so thatcommunication conflict is readily resolved between the variouscomponents within the analyte monitoring system 100.

In certain embodiments of the present disclosure, the sensor 101 isphysically positioned in or on the body of a user whose analyte level isbeing monitored. The sensor 101 may be configured to continuously samplean analyte level of the user and convert the sampled analyte level intoa corresponding data signal for transmission by the transmitter unit102. In certain embodiments, the transmitter unit 102 may be physicallycoupled to the sensor 101 so that both devices are integrated in asingle housing and positioned on the user's body. In certainembodiments, the transmitter unit 102 may perform data processing suchas filtering and encoding data signals and/or other functions. Datasignals received from sensor 101 correspond to a sampled analyte levelof the user, and transmitter unit 102 may transmit the analyteinformation to, among others, the primary receiver unit 104 via thecommunication link 103. Additional detailed description of continuousanalyte monitoring systems and various components including thefunctional descriptions of the transmitter are provided in, but notlimited to, U.S. Pat. Nos. 6,134,461, 6,175,752, 6,121,611, 6,560,471,6,746,582, and U.S. Patent Publication No. 2008/0278332 filed May 8,2008 and elsewhere, the disclosures of each of which are incorporated byreference for all purposes.

FIGS. 2A-2C illustrate an exemplary analyte monitoring device 200, suchas the primary receiver 104 of analyte monitoring system 100 (FIG. 1)that may be used with certain embodiments of the present disclosure. Incertain embodiments, the analyte monitoring device 200 is generallyrectangular in shape and sized to fit in a single hand of a user.However, it is contemplated that the analyte monitoring device 200 mayhave various other shapes and sizes depending on, for example, aparticular user or environment. For example, the analyte monitoringdevice 200 may have a first size and shape for an adult user, and asecond size and shape for a child user.

The analyte monitoring device 200 comprises a front housing 205 and aback housing 207. In one aspect, each of the front housing 205 and theback housing 207 may be replaceable with housing covers having variouscolors and/or designs. In certain embodiments, the analyte monitoringdevice 200 may also include grip portions 209 disposed on lateral sidesof the housing portions 205 and 207. The grip portions 209 may include aplurality of depressions or finger holds to provide a better grip to auser. Grip portions 209 may be made of rubber, plastic or other similarmaterial that may increase a user's grip.

In certain embodiments, a user interface is disposed on the analytemonitoring device 200. As used herein, user interface refers tocomponents that assist a user in interacting with the analyte monitoringdevice 200. Referring still to the Figures, the user interface mayinclude a display 210 and a plurality of input buttons 220 on the frontsurface of the analyte monitoring device 200. Although two input buttons220 are shown, it is contemplated that a keypad or keyboard may bedisposed on the front surface of the analyte monitoring device 200 oronly a single button or no buttons may be included. In certainembodiments, the user interface also includes a jog wheel 230 and asecondary button 240 disposed on one of the lateral sides of the analytemonitoring device 200. In certain embodiments, the user interface mayalso include a test strip port 250 for receiving an in vitro test stripand a data port 260, such as a USB or serial port. In certainembodiments, a sound system (not shown) may also be included with theuser interface for outputting audible signals. The sound system mayinclude a sound synthesizer (e.g., an OKI ML2871 sound generator) and atleast one speaker (e.g., an eight ohm speaker). In certain embodiments,a vibratory system may be included and configured for outputting, amongothers, a vibratory or other tactile alert. Although specific componentsare mentioned, it is contemplated that the user interface may includefewer or additional components than those specifically discussed.

In certain embodiments, the display 210 is an organic light emittingdiode (OLED) display. The OLED display may be configured with a displayresolution and refresh or frame rate conducive to a clear output to theuser. In one embodiment, the display may be a 160×128 pixel display witha frame rate of about 10.5 frames per second. In certain embodiments,the display may be higher resolution and/or refresh rate, including highdefinition (HD) output. Such a display 210, in aspects of the presentdisclosure, is configured to provide color output display. In otherembodiments, the display 210 is a liquid crystal display (LCD). In otherembodiments, the display is a plasma display. In certain embodiments,the display 210 is a touch sensitive display. The display 210 is used todisplay a plurality of graphical user interface screens or screen types(e.g. display screens) to a user as the user interacts with the analytemonitoring device 200. In certain embodiments, the display is configuredto output still and video images.

In certain embodiments, a zoom-in and zoom-out feature is available forvarious display screens that are output on the display 210. The zoom-inand zoom-out feature may be used by actuating the jog wheel 230 eitheralone, or in combination with, a second button, such as secondary button240 or one of the plurality of input buttons 220. The zoom-in andzoom-out feature enables a user to fully or partially display menuscreens having a plurality of menu items, all of which may or may not besimultaneously displayed on the display 210. Further, the zoom-in andzoom-out feature can be used to focus in on a particular portion of agraph or other type of information that is displayed on display 210. Incertain embodiments, the zoom-in and zoom-out feature may be used tozoom-in on a selected panel of a home screen such as will be describedin greater detail below.

In certain embodiments, display 210 outputs display screens in anorientation that corresponds to the analyte monitoring device 200 beingheld in a vertical upright position. In one aspect, the analytemonitoring device 200 includes an accelerometer configured to detect anorientation at which the analyte monitoring device 200 is being held.Based on the detected direction, a control unit or processor of theanalyte monitoring device 200 outputs display screens on the display 210in an orientation that corresponds to the detected orientation of theanalyte monitoring device 200. Thus, when the orientation of the analytemonitoring device 200 is changed, the orientation of the display screenson the display 210 are adjusted to conform to the new orientation. Forexample, if the analyte monitoring device 200 is in a vertical uprightor portrait position, the display screens output on the display 210 aredisplayed in a vertical upright or portrait orientation. However, if theanalyte monitoring device 200 is rotated 90 degrees, the display screensoutput on the display 210 will also rotate by 90 degrees in the samedirection, at which point the display screens output on the display 210will be shown in a landscape or horizontal orientation instead of avertical upright or portrait orientation.

In certain embodiments, if the analyte monitoring device 200 isrepeatedly rotated into a particular orientation for specificfunctionality, such as, for example, when performing a blood glucosetest, or when a particular graph is displayed, the display screenscorresponding to the specific functionality are output in an orientationthat corresponds to the expected orientation of the analyte monitoringdevice 200. For example, if a user repeatedly holds the analytemonitoring device 200 in a particular orientation (e.g. horizontally onits side) when performing a blood glucose test, a processor of theanalyte monitoring device 200 causes a blood glucose test display screento be output on the display 210 in an orientation corresponding to theexpected orientation of the analyte monitoring device 200 when inputcorresponding to a blood glucose test is received or detected. Incertain embodiments, the detected input may correspond to user selectedinput on the user interface, such as, for example, selecting a bloodglucose test menu item on a menu display screen or by inserting a teststrip into the test strip port 250. In other embodiments, theorientation of the display screens may be altered based on variousalarms and/or alert notifications.

The user interface of the analyte monitoring device 200 also includes aplurality of input buttons 220. In certain embodiments, at least one ofthe input buttons 220 is a power button and at least one input button220 is used to activate and deactivate a light in the test strip port250. As will be described in greater detail below, each input button 220may also be used as a softkey button such that actuation of the inputbuttons 220 invoke functions described by text of a softkey button labelshown on the display 210. Although two input buttons 220 arespecifically shown, it is contemplated that fewer or additional inputbuttons 220 may be included on the user interface of the analytemonitoring device 200.

Each of the input buttons 220 may also be programmed by a user to invokea number of different functions based on user preference. For example,actuation of one of the input buttons 220 may cause the analytemonitoring device 200 to enter a sleep mode. Other examples includecontrolling the volume of the analyte monitoring device 200 or turningwireless capabilities of the analyte monitoring device 200 on or off.The input buttons 220 may also be programmed by a user to act as ashortcut to a particular display screen (e.g., a timeline graph, CGMstatistics screen etc.).

In certain embodiments, analyte monitoring device 200 also includes ajog wheel 230 and a secondary button 240 disposed on a lateral side. Asused herein, a jog wheel refers to a physical scroll action control thathas inputs of “up”, “down” (e.g., scroll up and scroll down) and“select” (e.g., inward push of the jog wheel). In certain embodiments,jog wheel 230 may also include left and right scrolling action. Suchfunctions could also be carried out by respective up and down buttonsand a select button. Although a jog wheel is specifically mentioned, itis contemplated that other actuators, such as a ball or roller, may beused.

In certain embodiments, secondary button 240 is used as a “back” buttonto assist a user in navigating to various screen types and displayscreens of the user interface. In addition to enabling a user tonavigate backwards through the display screens, the secondary button 240may be used to cancel a change made to a user selectable value in thevarious display screens. In certain embodiments, when the user hasnavigated away from a home screen, actuation of the secondary button 240for a predetermined amount of time (e.g. 5 seconds) returns a user tothe home screen. In certain embodiments, the secondary button 240 is anadditional softkey button that can be programmed for specificfunctionality, such as accessing a particular graph or display screen,based on user preference.

In certain embodiments, the analyte monitoring device 200 also includesa test strip port 250 and a data port 260. In certain embodiments, thetest strip port 250 is used to receive a test strip to check a bloodglucose level of a user and/or to calibrate a sensor, such as, forexample, sensor 101 (FIG. 1). In certain embodiments, an illuminationassembly disposed within the housing of the analyte monitoring device200 is configured to illuminate the test strip port 250 of the analytemonitoring device 200.

Referring to FIG. 2D, the illumination assembly includes a light source280, such as, for example, a light emitting diode (LED), OLED,incandescent light bulb, cold cathode fluorescent lamp (CCFL) or solidstate laser, and a light pipe 270 configured to distribute light fromthe light source 280 to an opening in the test strip port 250 or variousother areas of the analyte monitoring device 200. In one aspect, theillumination assembly may be configured to produce a plurality ofcolors. For example, the light source 280 may produce a white light andas the white light passes through the light pipe 270, various filters inthe light pipe 270 may cause the white light to refract into variouscolors. Thus, a single light source 280 and light pipe 270 may be usedto illuminate a plurality of areas of the analyte monitoring device 200in various colors. For example, the light pipe 270 may be configured toilluminate a test strip port 250 of the analyte monitoring device 200 ina first color and illuminate one or more buttons, such as input buttons220, disposed on the housing of the analyte monitoring device 200 in asecond color. In another aspect, a plurality of light sources may beused with a single light pipe 270 in which each light source 280 emits adifferent color of light. In still yet another embodiment, a pluralityof light pipes 270 may be used with a single or a plurality of lightsources 280.

In certain embodiments, the light pipe 270 is a tubular or planarstructure, formed from clear or colored plastic or glass. As shown inFIG. 2D, at least a portion of the light pipe 270 is placed over thelight source 280 and is configured to distribute light from the lightsource 280 to a test site or entry port of the test strip port 250.Although a test site and an entry port are specifically mentioned, it isalso contemplated that the light pipe 270 may be used to illuminate anindicator icon, a keypad, and/or one or more buttons (e.g., inputbuttons 220, jog wheel 230, secondary button 240, etc.) disposed on theanalyte monitoring device 200. In yet another embodiment, portions ofthe housing of the analyte monitoring device 200 may be transparent orbe formed from one or more light pipes thereby enabling portions of thehousing of the analyte monitoring device to be illuminated by the lightsource 280.

In certain embodiments, the light pipe 270 includes a first end that issecured on or over the light source 280. In another embodiment, thefirst end of the light pipe 270 is secured to an area proximate thelight source 280. The light pipe 270 has a length that extends from thefirst end to a second end. In certain embodiments, the second end of thelight pipe is an entry port of the test strip port 250. Thus, when thelight source 280 is activated, light is emitted through the light pipe270 to the test site.

In one aspect, the second end of the light pipe 270 has an openingthrough which a test strip may be inserted. As such, the second end maybe shaped so as to assist a user in inserting a test strip. For example,the opening of the second end of the light pipe 270 may be tapered so asto allow the test strip to be initially inserted into the opening of thelight pipe 270 with relative ease.

It is contemplated that the light pipe 270 may have various shapes,sizes, and transparencies with each shape, size and transparencyaffecting the shape and strength of light emitted from the light pipe270. For example, depending on the shape of the light pipe 270, a“flashlight” effect may be produced whereby a test site or test strip isilluminated with a bright beam of light. In certain embodiments, thelight pipe 270 may include sharp prismatic type folds from which lightfrom the light source 280 is reflected. Further, a reflecting surfacemay be included in the light pipe 270 to increase the efficiency oflight transmission down the length of the light pipe 270. Examplesinclude a metalized surface or a coating on one or more prism faces orintermediate faces of the light pipe 270 to increase the internalreflection. In one aspect, the light pipe 270, or portions thereof(e.g., the first end or the second end) may be configured in a convex orconcave shape. In yet another aspect the light pipe 270 may have aroughened (e.g., pitted) surface to create a light dispersion effect.

In certain embodiments, the light pipe 270 may be used to providevarious aesthetics to the analyte monitoring device 200, such as, forexample, providing shape, color, and lighting to the overall design ofthe analyte monitoring device 200. For example, the light pipe 270 canprovide an illuminated icon or a distinctive design element such as, forexample, a trademark, or a model or brand of the analyte monitoringdevice 200. Further, and as described above, one or more light pipes 270may be used as part of the overall design of the analyte monitoringdevice 200.

In certain embodiments, the light source 280 is at least partiallydisposed on a top or bottom portion of the housing of the analytemonitoring device 200. In another embodiment, the light source 280 is atleast partially disposed on a printed circuit board 290 contained withinthe housing of the analyte monitoring device 200. In certainembodiments, the analyte monitoring device 200 contains only a singleprinted circuit board that supports and connects all of the electroniccomponents of the analyte monitoring device 200 including the lightsource 280. In certain embodiments, because the light pipe 270distributes light from the light source 280, additional printed circuitboards are not required to illuminate various portions or areas of thehousing of the analyte monitoring device 200. Thus, as multiple printedcircuit boards are not required, the overall reliability of the analytemonitoring device 200 is increased as inter-board connections betweenmultiple printed circuit boards are also not required. Further, incertain embodiments, the light pipe 270 may be used as part of thehousing and substantially, if not entirely, close portions of thehousing of the analyte monitoring device 200 that would otherwise beopen if light pipes 270 were not used to permit the light from the lightsource 280 to be emitted from the housing. As such, the light pipe 270also functions to protect the inner circuitry of the analyte monitoringdevice 200 from moisture, dust and other contaminants.

In certain embodiments, the light source 280 is controlled by useractivation of one or more of the input buttons 220 or secondary button240. In one aspect, the option to turn the light source 280 on or off isonly available when a test strip has been inserted into the test stripport 250. In another embodiment, the light source 280 may be turned onor off only when the display 210 has an active display screen and one ofthe input buttons 220 is depressed for a predetermined amount of time(e.g., 2 seconds). In still yet another embodiment, the light source 280is automatically activated when a test strip is correctly inserted intothe test strip port 250. It is also contemplated that an audible alertor tactile notification may be output when the test strip has beencorrectly inserted into the test strip port 250. Additionally, a warninglight and/or an audible notification may be output by the analytemonitoring device 200 if the test strip is incorrectly inserted into thetest strip port 250. For example, in certain embodiments, when the teststrip is correctly inserted into the test strip port 250, a control unitor processor of the analyte monitoring device 200 causes a first lightsource to emit a first color and a first audible alarm and/or tactilenotification may simultaneously be output. When the test strip isincorrectly inserted into the test strip port 250, a control unit orprocessor of the analyte monitoring device 200 causes a second lightsource to emit a second color (e.g., a red warning light) and a secondaudible alarm and/or second tactile notification may be output.

In certain embodiments, when the light source 280 has been actuated,such as, for example, when a test strip has been inserted into the teststrip port 250 or in response to user actuation of an input button 220,the light remains on for a predetermined amount of time (e.g., 2 minutesor 1 minute or 30 seconds). When the time period expires, a processor ofthe analyte monitoring device causes the light source 280 to turn off.In another embodiment, the light source 280 is turned off only inresponse to a user removing the test strip from the test strip port 250or when a user actuates one of the input buttons 220.

In certain embodiments, in addition to a light source 280 beingactuated, the display screen on the display 210 may change from a homescreen to a user instruction screen when the test strip is inserted intothe test strip port 250. In certain embodiments, the user instructionscreen is output on the display 210 if a blood sample or controlsolution cannot be detected on the test strip when the test strip isinserted into the test strip port 250. In certain embodiments, the userinstruction screen instructs the user on how to proceed with a bloodglucose test or a control solution test. In certain embodiments, forexample, an icon, graphic, series of graphics, animation, video and/ortext instructing a user to apply a blood sample or a control solution tothe test strip after the test strip has been inserted may be output onthe display 210. In another embodiment, audible voice instructions maybe provided along with the instruction screen to instruct the user onhow to proceed with the blood glucose test or control solution test.

In certain embodiments, while the test is being performed, an icon, suchas a circle comprised of four arrows (or another icon), may be output onthe display 210 and/or progress tones may be output to notify the userthat the blood glucose test is ongoing. In certain embodiments, the usermay input additional information into the analyte monitoring device 200using, for example, an input button 220, corresponding to whether acontrol solution was used or whether a blood sample was used on the teststrip. When the blood glucose test is complete, the test results areoutput on the display 210. For example, if the user performs a bloodglucose test and the user's blood glucose level is either lower than 20mg/dL (or other predetermined threshold) or higher than 500 mg/dL (orother predetermined threshold), a “Low” or a “High” indication isdisplayed. These results could indicate that the user is either in ahypoglycemic state or a hyperglycemic state or a hypoglycemic orhyperglycemic state is impending. In such cases, in certain embodiments,an alert screen may be output on the display 210 in which it isrecommended that the user contact a healthcare professional or takecorrective action, such as carbohydrate ingestion or taking medication,such as insulin.

In certain embodiments, data port 260 is a standard mini-USB port thatmay be used to charge a battery or other power source of the analytemonitoring device 200. Data port 260 may also be used to upload datastored in a memory or other storage medium of the analyte monitoringdevice 200 to a personal computer or secondary receiver. The stored datamay correspond to settings of the analyte monitoring device 200, orhistorical data such as blood glucose levels, continuously monitoredglucose levels etc. Data port 260 may also be used to download data froma server or other computing device, such as software upgrades,additional glucose alarm and notification tones including music,firmware upgrades and the like to the storage medium of the analytemonitoring device 200. When such updates are needed or finished, analert screen may be output on the display 210 of the analyte monitoringdevice 200 informing a user of a needed action (e.g., software upgradesavailable) or a completed action (e.g., download of additional tones iscomplete).

In certain embodiments, when a cable is inserted into the data port 260,such as a USB cable for a USB data port, for charging the analytemonitoring device and/or uploading data to/from the analyte monitoringdevice 200, a cover is provided over the test strip port 250 to preventa user from performing a blood glucose test when the analyte monitoringdevice 200 is connected to a power source. In one aspect, the cover maybe part of the USB cable. In another aspect, the cover may be part ofthe housing of the analyte monitoring device 200. As such, when thecable is inserted into the data port 260, the cover slides in front ofand closes the test strip port 250. When the cable has been removed fromthe data port 260, the cover is retracted into the housing of theanalyte monitoring device 200 and the test strip port 250 is accessible.

In certain embodiments, the analyte monitoring device is configured tooutput an audible alarm, a tactile alarm, a visual alert or acombination thereof when a test strip is inserted into the test stripport 250 while the analyte monitoring device 200 is connected to anexternal device or power supply (e.g., to charge a rechargeable batteryof the analyte monitoring device 200 and/or to transfer data between theanalyte monitoring device 200 and a remote computer). In suchembodiments, a processor of the analyte monitoring device 200 isconfigured to detect when the analyte monitoring device 200 isphysically connected (e.g., through a data cable, such as a USB or miniUSB cable connected to the data port 260) to an external device or powersupply. In certain embodiments, the processor is also configured todetect when a test strip has been inserted into the test strip port 250.As such, when a test strip has been inserted into the test strip port250, the processor is configured to issue a command to determine whetherthe analyte monitoring device 200 is, at the time of the insertion ofthe test strip, physically connected to an external device or powersupply. If the analyte monitoring device 200 is connected to an externaldevice or power supply, the processor issues a command to output thealert.

In one aspect the visual alert corresponds to an alarm screen such aswill be described in detail below, in which the user is visuallynotified that the analyte monitoring device 200 will not measure bloodglucose values when the analyte monitoring device 200 is physicallyconnected to an electronic device or a power source. In another aspectthe visual alert may be a warning light emitted from the illuminationassembly of the analyte monitoring device. In certain embodiments, upondetection of a test strip insertion into the test strip port 250,analyte monitoring device 200 may be configured to electrically isolatedata port 250.

In certain embodiments, various screen types are output on the display210 of the analyte monitoring device 200. Each screen type providesdifferent functionality, prompts and information to a user. Examplesinclude menu screen types and informational screen types. In certainembodiments, informational screen types include a plurality of displayscreens organized into a hierarchy of display screens. The displayscreens of the informational screen types typically, but notnecessarily, show graphs, connection status, alerts, warnings, and thelike. In certain embodiments, when informational screen type alerts,warnings or prompts are displayed, a processor of the analyte monitoringdevice 200 causes an alarm to be output if the alert is not acknowledgedwithin a predetermined amount of time (e.g. 1 hour). In certainembodiments, menu screen types include menus having selectable menuitems. Because the display screens are hierarchically arranged, uponselection of a menu item, the display screens linearly progress tovarious functions represented by the menu item (e.g., by actuation of asoftkey button corresponding to a “Next” softkey label), additionaldisplay screens or further submenus. Although specific screen types havebeen mentioned and will be described in further detail below, it iscontemplated that various other screen types may be included in the userinterface of analyte monitoring device 200.

FIG. 3A illustrates an information mode home screen 300 according toembodiments of the present disclosure. Referring to FIG. 3A, theinformation mode home screen 300 includes a plurality of panels orsections. In certain embodiments, the panels are distinct from oneanother and the information. Thus, what is displayed in one panel maynot necessarily affect what is displayed in a second panel. Furthermore,each panel or section may display different types of data to a user andthe data in each panel is dynamically updated. For example, one panelmay display user state information while a second panel simultaneouslydisplays system state information. Further, as information is received,such as, for example, continuous glucose data from the sensor 101 (FIG.1), the information displayed in the panels is updated to display thenewly received data. In certain embodiments, each panel is selectable.When a panel is selected, such as, for example, using the jog wheel 230(FIG. 2C) to highlight a particular panel or by user actuation of aninput button 220 or touch screen portion of the display 210, a user mayzoom in on the information displayed in the panel or select that theparticular panel be displayed on the entire area of the display 210.Furthermore, each of the panels may be sizable with respect to otherpanels. Thus, a user may select that one panel have a first size while asecond panel have a second size relative to the first panel. In anotherembodiment, the panels can be arranged in different positions relativeto one another based on user preference.

In certain embodiments, user state information includes informationcorresponding to analyte levels such as, for example, glucose levels,rate of change of an analyte level, bolus insulin doses, meals, exerciseperiods and other user related activities. This information may berepresented as text, numbers, graphics, icons, animations, video, orcombinations thereof.

In certain embodiments, system state information includes informationcorresponding to the status of various components of the analytemonitoring system 100 (FIG. 1) or the analyte monitoring device 200.Such information may include sensor status, calibration status,transmitter power status, alarm status, and battery status, amongothers. System state information may be represented as text, numbers,graphics, icons, animations, video, or combinations thereof.

In certain embodiments, various color schemes are used to convey aseverity of a condition that the system state information and the userstate information represent. As will be described in greater detailbelow, if for example, a numerical display of a current glucose value isoutput on the user state information panel, the number may be shown inpurple to indicate that the user's current glucose level is above apredetermined glucose threshold. If however, the number representing thecurrent glucose value displayed is green, the user's current glucoselevel is within the predetermined glucose threshold. While specificdisplays and colors are described, it is contemplated that anycombination of displays and colors may be utilized.

Referring back to FIG. 3A, information mode home screen 300 includes anumber of panels with each panel displaying a different type of data. Afirst panel 303 shows a user's historical analyte data, such as, forexample, continuous glucose levels. This data may be represented as agraph 305. As new data is received, such as, for example, glucose datafrom the sensor 101 (FIG. 1), the graph 305 is dynamically updated suchthat the newly received glucose data is displayed on the graph 305.Although graph 305 is depicted as a line graph, it is contemplatedvarious other types of graphs may be used including bar graphs, piecharts etc. Graph 305 includes a graph line 310 that representscontinuous glucose readings taken over a time t. Graph 310 also includeslower glucose target indicator 312 and an upper glucose target indicator314. In certain embodiments, the graph 305 includes a range of numberscorresponding to glucose levels. FIG. 3A illustrates a range of from 40mg/dL to 280 mg/dL on the y-axis with tick marks 316 at 40 mg/dL, 100mg/dL, 160 mg/dL, 200 mg/dL, and 280 mg/dL respectively, however, anysuitable range may be used. The graph 305 may also be configured todisplay a range of numbers in various units of measure. For example,graph 305 may display a range on the y-axis from 2 mMol/L to 16 mMol/Lwith tick marks at 2 mMol/L, 6 mMol/L, 8 mMol/L, 12 mMol/L, and 16mMol/L respectively.

In certain embodiments, the graph line 310 indicates historical analytedata, such as, continuous glucose readings. The graph line 310 of thegraph 305 may show up to 288 or more of the most recently loggedcontinuous glucose readings. In certain embodiments, more or lessrecently logged readings may be displayed. In certain embodiments, thenumber of recently logged readings to display may be user selectable. Incertain embodiments, the graph line 310 is displayed in a particularcolor so as to enable the user to easily distinguish the graph line 310from other icons or lines on the graph 305. In another embodiment,various portions of graph line 310 may be displayed in multiple colors.For example, when the graph line 310 is within the bounds set by lowerglucose target indicator 312 and upper glucose target indicator 314, thegraph line 310 is white. However, when the graph line 310 exceeds thethreshold levels set by the glucose target indicators 312 and 314, theportion of the graph line 310 that falls outside the target indicators312 and 314 is displayed as a second color. In one aspect, if the graphline 310 falls outside the target indicators 312 and 314 the entiregraph line 310 is displayed in a different color (e.g., purple). As willbe explained in greater detail below, when the graph line 310 exceeds athreshold level, an alarm icon may be displayed on the graph 305 toindicate that an alarm was output when the user's analyte level exceededthe threshold level.

In certain embodiments, a threshold value is exceeded if a data point,such as a glucose reading, has a value that falls outside of thethreshold values. Data points that exceed the threshold could indicatean impending condition, such as impending hyperglycemia or impendinghypoglycemia, or a particular present condition, such as hypoglycemia orhyperglycemia. For the purpose of illustration, when a data point on thegraph line 310 corresponds to a glucose level of 200 mg/dL and theselected upper threshold value 314 is 180 mg/dL, this could indicatethat the monitored user has entered a hyperglycemic state. However, whena data point on the graph line 310 corresponds to a glucose level of 65mg/dL and the selected lower threshold value 312 is 70 mg/dL, this couldindicate that the monitored user has entered a hypoglycemic state.

Referring still to FIG. 3A, lower glucose target indicator 312 and upperglucose target indicator 314 may be represented as horizontal lines anddisplayed in a different color than the color of the graph line 310.Although solid lines are shown, it is contemplated that dashed lines orother indicators may be used to designate the lower glucose targetindicator 312 and the upper glucose target indicator 314. As will beexplained in greater detail below, the values corresponding to the lowerglucose target indicator 312 and the upper glucose target indicator 314may be changed by a user. In another embodiment, the values of the lowerglucose target indicator 312 and the upper glucose target indicator 314may only be changed by a healthcare professional. In such cases, a menuscreen allowing a user to change the lower glucose target indicator 312and the upper glucose target indicator 314 may be locked and/or passwordprotected to prevent a user from changing the threshold range valueswithout permission or authorization from a healthcare professional,parent or guardian.

In certain embodiments, graph 305 includes event data icons 318 (FIG.3C). The event data icons 318 are displayed on the graph line 310 at thetime the event takes place. In certain embodiments, up to twenty of themost recent events can be displayed on the graph 305 at a single time.Thus, a user may readily identify a glucose level at the time the eventtook place and how the event affected the user's glucose level. Suchevents may include discrete blood glucose measurements, insulin dosing,exercise periods, meal times, state of health, and the like. Graph 305may also display alarm icons that indicate when particular alarms, suchas a high glucose threshold alarm, a low glucose threshold alarm, aprojected high glucose alarm, and a projected low glucose alarm, wereoutput by the analyte monitoring device 200. In certain embodiments, auser may create custom events and select icons, text or other indicatorfor each custom event. An exemplary graph having custom event indicators401 is shown in FIG. 4E. It is contemplated that a user may selectdistinguishing icons for each event, or class of events.

In certain embodiments, when an event icon 318 is displayed on the graph305, a user may select a particular event represented by the event dataicon 318. Upon selection of the event, a display screen is outputdisplaying details corresponding to the selected event. In one aspect,the selection of the event may be made using a touch screen or actuationof a softkey button, such as one of input buttons 220 (FIG. 2A), or byactuating the jog wheel 230 (FIG. 2C).

In certain embodiments, a second panel 320 of the information mode homescreen 300 is configured to simultaneously display glucose information322 and a trend information icon 324. The glucose information 322 may benumerically displayed and represent continuous glucose data receivedfrom the sensor 101 via the transmitter unit 102. In one aspect, asglucose data is received from the sensor 101, the glucose information322 is dynamically updated to show the most recent glucose readings. Incertain embodiments, the glucose information 322 is color coded toindicate whether the current glucose levels are within predeterminedthreshold levels. For example, the glucose information 322 may bedisplayed in green to indicate that the current glucose level of theuser is within a predetermined glucose threshold level. If however, theglucose information 322 is displayed in purple or yellow, the currentglucose level is above or below the predetermined threshold level.Although specific color combinations have been discussed, it iscontemplated that other color combinations may be used and/or selectedby a user.

In certain embodiments, fluctuations caused by noise, outlying datapoints, insignificant analyte changes and lag spikes are not displayedon either the first panel 303 or the second panel 320 of the informationmode home screen 300. In certain embodiments, “sticky” analyte valuesmay be used to ensure that the fluctuations are not displayed in eitherthe glucose information icon 322 and/or the trend information icon 324.For example, when a first new analyte level value is received from asensor, such as for example from sensor 101 (FIG. 1) via a transmitterunit 102, and the new value is higher than a sticky analyte value, thesticky analyte value is displayed. When a second new analyte value isreceived, the second new analyte value is compared to the sticky analytevalue. If the second new analyte value is also higher than the stickyanalyte value, the second new analyte value becomes the new stickyanalyte value and the second new analyte value is output on the display210 and/or used to calculate the rate of change. If the second newanalyte value is lower than the sticky analyte value, the current stickyvalue is maintained and displayed.

For example, if the most recently received analyte value is 99 mg/dL andthe first new analyte value is 102 mg/dL, the previously receivedanalyte value (e.g., 99 mg/dL) is designated as the sticky value and isoutput on the display 210. If the next analyte value received is alsogreater than 99 mg/dL (e.g., 101 mg/dL) the second new analyte value isdisplayed in place of the sticky analyte value (e.g. 99 mg/dL). However,if the second new value is less than 99 mg/dL, the sticky value is notreplaced.

In certain embodiments, if the received analyte values continue to movein the same direction (e.g. the analyte values increase or decrease)over a predetermined amount of time (e.g. 3 minutes), each new analytevalue that is received is displayed as it is received. In certainembodiments, each new analyte value that is received is displayed andreplaced by a subsequent analyte value until the readings stabilize(e.g., the rate of change of the analyte levels is within apredetermined threshold) for a predetermined amount of time (e.g. 5minutes). Once the analyte readings stabilize, the use of sticky valuesmay be implemented once again. Although the example above specificallyillustrates situations in which the received analyte level is higherthan the sticky value, it is contemplated that sticky values may be setfor analyte readings that are lower than the sticky analyte value in thesame way.

In certain embodiments, a dead zone, or threshold, may be created aroundthe sticky analyte value. In such cases, the displayed analyte valuedoes not change until the newly received value is outside of the deadzone. In certain embodiments, the dead zone boundary is defined by apercentage of change of the sticky analyte value or a range of thechange of the received analyte level value. For example, if the stickyanalyte value is 99 mg/dL, the dead zone may be defined as +/−4 mg/dL.Thus, the range of the dead zone is between 95 mg/dL and 103 mg/dL. Ifthe received analyte value is 102 mg/dL, the received analyte value isnot displayed because the received analyte value is within the deadzone. However, if a subsequent analyte value is received which isoutside the dead zone, for example, 104 mg/dL, the subsequent analytevalue is displayed and the dead zone resets. Thus, the new dead zone isbetween 100 mg/dL and 108 mg/dL. In certain embodiments, the dead zoneremains constant. Thus, regardless of the sticky analyte value, therange of change remains constant (e.g., +/−4 mg/dL). In anotherembodiment, the dead zone may be computed based on detected noise from asensor or fluctuations of the glucose value.

In certain embodiments, changes in analyte values that fall outside apredetermined range (e.g. +/−3 mg/dL) are the only analyte values outputon the display 210. For example, if analyte values of 90 mg/dL, 98mg/dL, 102 mg/dL, 100 mg/dL, 99 mg/dL, and 101 mg/dL, are received atthe analyte monitoring device 200 and the predetermined range is +/−3mg/dL, analyte values of 90 mg/dL, 98 mg/dL, 102 mg/dL, 102 mg/dL, 102mg/dL, and 102 mg/dL are output on the display 210 because not all ofthe received analyte values exceed the predetermined range.

In certain embodiments, a limit on the rate of change of the analytedata may be imposed. For example, the rate of change in the analytevalue may be limited to some maximum value, such as, for example, +/−4mg/dL per minute. If the rate of change of received analyte valuesexceeds the maximum value, the received analyte value is an outlyingdata point and will not be output on the display. While specific deadzone and other ranges are described, it is contemplated that otherapplicable range values may be used.

Returning to FIG. 3A, in certain embodiments, visual, tactile and/orauditory alarms may be used in conjunction with the data that is outputon the second panel 320. For example, when the current glucose level isabove or below a target level, an alert may be output and the panelcontaining the glucose information 322 is enlarged so as to be displayedon all, or substantially all, of the display 210 (FIG. 2A). The text ofthe glucose information 322 may be color coded based on a severity ofthe condition or color coded depending on a detected event thattriggered the alarm. For example, if the current glucose level is abovea predetermine threshold, when the panel expands, the text indicatingthe current glucose level of the user displayed in the panel is purple.In another embodiment, a processor or control unit of the analytemonitoring device 200 may cause a tactile and/or audible alarm to beoutput to notify the user that their current glucose level has exceededa threshold. If the user disregards the alarm, or uses a “snooze”feature, the alarm is output a second time after a predetermined or userselected amount of time has elapsed. In certain embodiments, if an alarmis unheeded by the user for a substantial period of time, the alarm mayincrease in volume or pitch or change tone, or an alarm on a secondaryanalyte monitoring device or an alarm on a computing device capable ofwirelessly communicating with the analyte monitoring device 200 may beoutput.

Referring back to FIG. 3A, in certain embodiments, the second panel 320also includes a trend information icon 324. The trend information icon324 indicates a rate of change of a user's glucose level and thedirection of the change. For example, a substantially horizontal trendarrow indicates glucose is changing gradually (e.g., less than 1 mg/dLper minute), a diagonally downward arrow indicates glucose is decreasingmoderately (e.g., between 1 and 2 mg/dL per minute), a straight downwardarrow indicates glucose is decreasing rapidly (e.g., more than 2 mg/dLper minute), a diagonally upward arrow indicates glucose is increasingmoderately (e.g., between 1 and 2 mg/dL per minute) and a straightupward arrow indicates glucose is increasing rapidly (e.g., more than 2mg/dL per minute). In certain embodiments, the trend information icon324 is dynamically updated based on data received from the sensor 101.Additionally, in certain embodiments, the trend information icon 324 iscolor coded based on a rate of change. For example, the straight upwardarrow may be displayed in red to indicate a rapid increase in the user'sglucose levels while the horizontal arrow may be displayed in green toindicate that the user's glucose levels are stable or are only graduallychanging.

Although an arrow is specifically described and shown in FIG. 3A, it iscontemplated that other icons, text, or graphics may be used to indicateglucose trends. Such examples include, but are not limited to trendindicator displays such as shown in FIGS. 3D-3E, in which arrows 386 and387 point to a plurality of indicator positions 388 and 389 thatcorrespond to rates of change of a glucose level, thermometer typegraphs such as shown in FIGS. 3F-3G, in which indicator bars 391 and 392of the graph change color based on the rate of change of the glucoselevel (e.g., the more bars that are filled indicate a greater rate ofchange), and speedometer type graphs such as shown in FIGS. 3H-3I, inwhich indicators 394 and 396 move continuously between regions 398 ortick marks 399 of the graph with each region 398 or tick mark 399representing a rate of change. In one aspect, a user may select any ofthe above indicators to be output on the display based on userpreference. It is also contemplated that each indicator described abovemay be color coded based on severity of the rate of change and/or onuser preference.

FIG. 3J illustrates a graphical display screen 395 showing measuredanalyte levels plotted against a rate of change of analyte levelsaccording to embodiments of the present disclosure. In certainembodiments, the graphical display screen 395 is included as a panel ofa home screen such as information mode home screen 300. In anotherembodiment, the graphical display screen 395 is a display screen that isoutput based on user settings, user navigation to the graphical displayscreen 395 or user actuation of an input button 220.

As shown in FIG. 3J, the graphical display screen 395 includes a line397 that indicates historic recorded analyte levels over a period oftime with the most recent analyte level represented by an arrowhead.Although an arrowhead is shown on the line 397, the arrowhead isoptional and other icons or markers may be used to indicate a mostrecent analyte level reading. In certain embodiments, the length of timerepresented by the line 397 is configurable by the user. As themonitored length of time is adjusted by the user, the length of the lineis also adjusted accordingly. For example, to highlight the recentchanges in the analyte level to assist a user in making medicationdosing decisions, the user may specify a short time range and thus, ashort line 397 is displayed on the graphical display screen 395. Usingthe graphical display screen 395, a user can visually distinguishbetween a high analyte level that is increasing (e.g. the line 397 istrending toward the upper right quadrant) versus a high analyte levelthat is decreasing (e.g., the line is trending downward from the upperleft quadrant).

In certain embodiments, the user may specify a long time range. Thus, ifa user's analyte levels remain constant or substantially constant, theline 397 forms small circles around the target analyte level. A user maythen visually distinguish large excursions that occur because the line397 falls outside of the smaller circles.

In one aspect, different color indicators or different grayscale levelsmay be used to indicate to a user how much time has elapsed since thereceived analyte levels were within a quadrant corresponding to aparticular rate of change or analyte level. Further, the graphicaldisplay screen 395 may display an indicator corresponding to how long auser's analyte levels have been in a certain zone or quadrant or thetime elapsed from a particular event such as a meal or an exerciseperiod.

Referring back to FIG. 3A, in certain embodiments, either one of thefirst panel 303 or the second panel 320 of the information mode homescreen 300 may not have data to display. In such cases, hash marks orother indicators may be output in one of the first panel 303 or thesecond panel 320 to indicate data is not available for that particularpanel. Such cases may be present when a sensor is currently active butno data has been received, data was lost or is unavailable, or the datahas been masked for a specified amount of time.

In certain embodiments, when the information mode home screen 300 isdisplayed and a user actuates the jog wheel 230 or an input button 220,at least one of panels 303 or 320 may be replaced with a sensor lifeindicator screen (not shown). The sensor life indicator screen maydisplay the current sensor life, such as for example, the sensor liferemaining for sensor 101 (FIG. 1) and provide information (e.g., a graceperiod) as to if/when the current sensor needs to be replaced. This datamay be shown as text, an icon, a graphic, an animation, a video, or acombination thereof. It is also contemplated that auditory and/orvibratory or other tactile alarms may be output in conjunction with thesensor life indicator screen to notify a user that the sensor needs tobe replaced or will need to be replaced within a given period of time.In certain embodiments, a graph showing the signal strength, the chargeremaining in the battery of the analyte monitoring device 200 and/or thecharge remaining on the battery of the transmitter may be output anddisplayed in one or more panels or on sensor life indicator screen.

In certain embodiments, information mode home screen 300 may alsoinclude system information icons on a portion or panel of theinformation mode home screen 300. In certain embodiments, the systeminformation icons indicate the status of various system components. Suchicons may include a wireless connection icon 330, an audio/vibratorysettings icon 332, a calibration status icon 334, and battery icon 336.Although not shown, other icons may be displayed including a sensor lifeicon that shows the remaining life of a sensor, such as, for example,sensor 101 or an alarm notification icon indicating that an alarm oralert condition is detected. In certain embodiments, home screen 300 mayalso show the current date 338 and the current time 340. As with otherinformation displayed on display 210, the date and time may be displayedas color coded numbers, text, an analog clock or a combination thereof.

The wireless connection icon 330 shows the status of the wirelessconnection between the transmitter, such as transmitter unit 102 (FIG.1), and the analyte monitoring device 200. When a connection between thetransmitter and the analyte monitoring device 200 is established, thewireless connection icon 330 is output on the display indicating theconnection has been made. However, when a connection has not beenestablished between the transmitter and the analyte monitoring device200, a second form of the wireless connection icon 330 is output on thedisplay to indicate a connection has not been established. For example,when the connection is established between the transmitter and theanalyte monitoring device 200, the wireless connection icon 330 isoutput on the display 210 with connection strength indicators as shownin FIG. 3A. When a connection has not been established between theanalyte monitoring device 200 and the transmitter, the wirelessconnection icon 330 is output showing a small “x” disposed by or on thewireless connection icon 330. In one aspect, the wireless connectionicon 330 is output according to the signal strength of the connectionbetween the analyte monitoring device 200 and the transmitter. Forexample, additional connection strength indicators may be displayed nextto the wireless connection icon 330 or the wireless connection icon 330may be displayed in a bright color to indicate a strong connection isestablished between the analyte monitoring device 200 and thetransmitter. If a weak connection is established between the analytemonitoring device 200 and the transmitter, the wireless connection icon330 is output in a different color or has fewer connection strengthindicators. Although specific indicators are mentioned, it iscontemplated that various other indicators may be used to show, forexample, connection strength. Although a wireless connection isspecifically mentioned, it is contemplated that various connectionprotocols may be used including, a Bluetooth® connection, a ZigBeeconnection, a radio frequency (RF) connection, a radio frequencyidentification (RFID) connection, an infrared connection, and a wiredconnection.

In certain embodiments, audio/vibratory settings icon 332 shows theaudio and/or vibratory settings for the analyte monitoring device 200.In other embodiments, audio and vibratory settings may be displayed asseparate icons or indicators. In certain embodiments, theaudio/vibratory settings are applied to glucose readings, data loss, andvarious system alarms. Various icons may be used to represent thevarious settings available, such as, for example, an audio and vibratesetting in which the audio/vibratory setting icon 332 is output showinga note being surrounded by vibration signals, an audio only setting inwhich the audio/vibratory setting icon 332 is output showing only anote, a vibrate only setting in which the audio/vibratory setting icon332 is output showing a plurality of vibration signals or a mute settingin which the audio/vibratory setting icon 332 is output showing a notehaving a line or an “x” therethrough. It is also contemplated that theoverall volume of the analyte monitoring device 200 may be displayed bythe audio/vibratory icon 332. For example, if the overall volume of thesystem is high, the audio/vibratory icon 332 may be output in a firstcolor, while if the overall volume of the system is low, theaudio/vibratory icon 332 may be output in a second color.

In certain embodiments, calibration status icon 334 is output on thedisplay to notify a user that a sensor, such as, for example, sensor 101(FIG. 1) should be calibrated. In certain embodiments, a control unit orprocessor of the analyte monitoring device 200 outputs an alarm and/oralert screen to notify a user that the sensor should be calibrated. Forexample, when a predetermined time period has elapsed since the lastcalibration, an alarm is output a predetermined number of times and ablood drop icon is output on the display. In certain embodiments,different icons may be output on the display 210 based on various sensorcalibration statuses. For example, output of a blood drop icon on thedisplay 210 may indicate that it is time to calibrate the system, whilean hourglass icon output on the display 210 may indicate that the sensorshould be calibrated but the system is not ready for the calibration. Inone aspect, output of an hourglass icon may indicate that glucoseresults are temporarily unavailable. In certain embodiments, a blooddrop icon or hourglass icon may be output on the display 210 with aplurality of fill indicators to indicate a time period remaining untilthe sensor should be calibrated. For example, if the sensor should becalibrated in 10 hours, the two out of four fill indicators of the blooddrop icon may be output on the display 210. If the sensor should becalibrated in 4 hours, one out of four fill indicators of the blood dropicon are output on the display 210. In another embodiment, thecalibration status icon 334 may be output in various colors based on anexpected calibration time. For example, if 10 hours remain until anexpected sensor calibration time, the calibration status icon 334 isoutput in a first color (e.g., green). When 4 hours remain until anexpected sensor calibration time the calibration status icon 334 isoutput in a second color (e.g., red).

In certain embodiments, battery icon 336 represents the percentage ofcharge remaining in a battery of the analyte monitoring device 200.Although not shown, a similar battery icon may be output on the displayto indicate the percentage of charge remaining in the battery of thetransmitter, such as, for example, transmitter unit 102 (FIG. 1). Incertain embodiments, the battery icon 336 is output having at least fourindicators with each of the indicators representing 25% of the batterylife. As battery life of the analyte monitoring device 200 drains, eachof the indicators of the battery icon 336 is output in a differentcolor. For example, as battery life is depleted from a 100% charge to a75% charge, a processor or output unit of the analyte monitoring device200 causes the first indicator of the battery icon 336 to change fromgreen, to yellow to red to indicate that the user is reaching 75% chargewhile the remaining three indicators of the battery icon are output ingreen. As battery life of the analyte monitoring device 200 iscontinually depleted, the remaining three indicators are output indifferent colors to indicate the percentage of battery life left in theanalyte monitoring device 200. In certain embodiments, the battery icon336 may also indicate whether the analyte monitoring device 200 iscurrently being charged. When the analyte monitoring device 200 is beingcharged, each of the four indicators of the battery icon 336 may beoutput in different colors in a similar manner as discussed abovealthough in the opposite color order. For example, when the battery ofthe analyte monitoring device 200 is being charged from 75% to 100% thecolor of the first indicator of the battery icon 336 is output from redto yellow to green to indicate the status of the charge. In anotherembodiment, the battery icon 336 may be output in various colorsdepending on the amount of charge remaining in the battery of theanalyte monitoring device 200. In certain embodiments, flashing and/orfading of the battery icon may be used in lieu of or in conjunction withthe colors to indicate battery status. In certain embodiments, more orless than four indicators may be used to indicate battery status, or asingle dynamic indicator may be utilized.

Although specific icons have been discussed with respect to each of thewireless connection icon 330, the audio/vibratory settings icon 332, thecalibration status icon 334, and the battery icon 336, it iscontemplated that various icons, text, graphics, animations, and/orvideo in varying colors, shades and levels of brightness may be outputto indicate a status of the various components of the analyte monitoringdevice 200 or the analyte monitoring system 100 (FIG. 1).

In certain embodiments, information mode home screen 300 also includessoftkey labels 342 and 344. In certain embodiments, each softkey label342 and 344 is outlined to help distinguish the label from the othericons and text on the information mode home screen 300. Further, eachsoftkey label 342 and 344 specifies actions that occur when acorresponding input button 220 (FIG. 2A) is actuated or when a touchsensitive area of the display 210 corresponding to the softkey labels342 and 344 are touched. For example, if the input button 220corresponding to softkey label 342 is actuated, a full screen graph,such as, for example, timeline graph 400 (FIG. 4 a) will be output onthe display 210 of the analyte monitoring device 200. If however, theinput button 220 corresponding to softkey label 344 is actuated, a menu,such as, for example, menu screen 600 (FIG. 6) will be output on thedisplay 210 of the analyte monitoring device 200. Although specificsoftkey labels have been discussed, it is contemplated that variousother softkey labels may be used. It is also contemplated that thesoftkey labels may be user selectable to enable a user to customizewhich features and data may be accessed directly from the informationmode home screen 300. In certain embodiments, the analyte monitoringdevice 200 may “learn” which functions and display screens are used bythe user most frequently and automatically update the softkey labelsaccordingly. For example, if a processor or control unit of the analytemonitoring device 200 detects that a user is consistently accessing aparticular menu screen, a softkey label corresponding to that particularmenu screen will be output on the information mode home screen 300.Although two softkey labels are shown in FIG. 3A, it is contemplatedthat any number of softkey labels may be output on the display 210.

FIG. 3B illustrates an activity mode home screen 350. According tocertain embodiments, the activity mode home screen 350 includes aplurality of panels or screens that may be used to display informationto a user. As with the information mode home screen 300 (FIG. 3A) someof the panels of the activity mode home screen 350 may display userstate information while other panels of the activity mode home screen350 show system state information. For example, panel 360 may beconfigured to display glucose information 322 and trend information icon324 as described above with reference to FIG. 3A. Additionally, panel370 may be configured to display system information icons such as awireless connection icon 330, an audio/vibratory settings icon 332, acalibration status icon 334, and battery icon 336 as previouslydescribed. Activity mode home screen 350 may also include a timeindicator 340, a date indicator (not shown) and a plurality of softkeylabels 342 and 344 as were described above with reference to FIG. 3A.

In certain embodiments, activity mode home screen 350 includes a thirdpanel 380 that includes a menu 385 with user selectable menu items. Asshown in FIG. 3B, the menu items may include an alarms menu item, astatus menu item, a reports menu item, an add event menu item, and asettings menu item. Each menu item has specific functionality, displayscreens or submenus associated therewith, each of which will bedescribed in greater detail below. In certain embodiments, each menuitem may be selected by a user actuating a jog wheel, such as, forexample, jog wheel 230 (FIG. 2C). When a particular menu item ishighlighted, such as, for example, the alarms menu item as shown in FIG.3B, a user may select the highlighted item by either pressing an inputbutton 220 or by pressing the jog wheel 230 inwardly to select thehighlighted item. In certain embodiments, when the display 210 is atouch sensitive display, the user may simply touch the menu item outputon the display to make a selection.

FIG. 3C illustrates an alternative arrangement of an information modehome screen 390 according to embodiments of the present disclosure. Aswith information mode home screen 300, information mode home screen 390includes a first panel 302 that displays a user's historical analytedata represented as a graph 305. The graph 305 includes a graph line 310that represents continuous glucose readings taken over a time t, lowerglucose target indicator 312 and an upper glucose target indicator 314.In certain embodiments, the graph 305 may also include event data icons318 that represent various events of the user during the time period thegraph represents. Examples of such events include, but are not limitedto, discrete blood glucose measurements, insulin dosing, meal times, andexercise periods.

Information mode home screen 390 may also be configured to displayglucose information 322 and trend information icon 324 as describedabove with reference to FIG. 3A. Additionally, information mode homescreen 390 may include a third panel 370 configured to display systeminformation icons such as a wireless connection icon 330, anaudio/vibratory settings icon 332, a calibration status icon 334, andbattery icon 336 as well as a time indicator 340, a date indicator (notshown) and a plurality of softkey labels 342 and 344 as were describedabove with reference to FIG. 3A.

FIG. 4A illustrates a display screen showing a timeline graph 400according to embodiments of the present disclosure. The display screenshowing the timeline graph 400 may be output on the display when aninput button 220 (FIG. 2A) is actuated that corresponds to a “Graph”softkey label such as, for example, softkey label 342 (FIG. 3A).

In certain embodiments, the timeline graph 400 includes similar displayfeatures as those described above with reference to FIG. 3A. Forexample, timeline graph 400 includes a graph line 310 that representscontinuous glucose readings. User-selectable lower glucose targetindicator 312 and upper glucose target indicator 314 may also bedisplayed on the timeline graph 400. In certain embodiments, thetimeline graph 400 is configured to display a range of numberscorresponding to glucose level, such as from 40 mg/dL to 280 mg/dL onthe y-axis with tick marks 316 at various points within the range, suchas at 40 mg/dL, 100 mg/dL, 160 mg/dL, 220 mg/dL, and 280 mg/dL. Althoughspecific tick mark values are mentioned, it is contemplated additionaltick mark values may be used. For example, if a user uses a zoom-infeature, the tick marks may have different values (e.g., 60 mg/dL, 70mg/dL, 80 mg/dL, 90 mg/dL, and 100 mg/dL) corresponding to how close theuser zoomed-in on the timeline graph 400. In certain embodiments, ifglucose values fall below a lower threshold, such as 40 mg/dL or climbabove an upper threshold, such as 280 mg/dL, the timeline graph 400displays those values at 40 mg/dL or 280 mg/dL respectively. Thetimeline graph 400 may also be configured to display a range of numberson the y-axis in various units of measure, such as a range from 2 mMol/Lto 16 mMol/L with tick marks at 2 mMol/L, 6 mMol/L, 8 mMol/L, 12 mMol/L,and 16 mMol/L respectively.

As described above, in certain embodiments, graph line 310, lowerglucose target indicator 312 and upper glucose target indicator 314 maybe output in various colors so a user may more readily identify pointsof interest on the timeline graph 400. Additionally, valuescorresponding to each of the lower glucose target indicator 312 and theupper glucose target indicator 314 may be changed by a user or changedby a healthcare professional.

In certain embodiments, timeline graph 400 may also include event dataicons 318. The event data icons 318 are placed at locations on the graphaccording to the time at which the event took place and/or inconjunction with the monitored glucose level depicted by the graph line310. Such events may include alarms or alerts, discrete blood glucosemeasurements, insulin dosing, exercise periods, meal times, state ofhealth, and the like. In certain embodiments, particular event dataicons, such as blood glucose reading icons, and custom event icons, maybe placed on the graph according to continuous glucose monitoring levelsand/or times in which the events took place without simultaneouslyshowing a graph line, such as shown in FIG. 4E. Still referring to FIG.4E, a user may select an earlier date represented by the graph or laterdate represented by the graph by actuating input buttons 220 havingcorresponding softkey labels 440 and 450.

Referring back to FIG. 4A, as shown, each event may have a correspondingicon to enable a user to more readily identify what activities tookplace at certain times and which activities, if any, may have caused anincrease or decrease in glucose levels. In certain embodiments, the usermay select an event depicted by the event data icon 318 and view detailson that particular event. The selection may be made by highlighting theparticular event using a jog wheel 230 (FIG. 2C) or input button 220(FIG. 2A) and then selecting the highlighted event icon. If a touchsensitive display is used, a user may touch the icon on the display toview the details of the selected event.

In certain embodiments, timeline graph 400 also displays a time periodsetting 410 and a date 420 that the timeline graph 400 represents. Forexample and as shown in FIG. 4A, the time period selected is 24 hoursand the date is Aug. 20, 2009. Thus, the timeline graph 400 showscontinuous glucose readings for a complete 24 hour period as indicatedby the time periods 430. If the jog wheel 230 (FIG. 2C) is actuated, auser may chronologically view previous or subsequent 24 hour timeperiods of the timeline graph 400. In certain embodiments, the timeperiod setting 410 may be adjusted by a user and may include varioustime periods, such as, for example, 2 hour time periods, 4 hour timeperiods, 6 hour time periods, 12 hour time periods or 24 hour timeperiods, or others. In certain embodiments, regardless of which timeperiod setting is used, the timeline graph 400 is output showing onlythe selected time period (e.g. 2 hours).

In certain embodiments, softkey button labels 440 and 450 are alsoincluded on the timeline graph 400 display screen. In certainembodiments, when a corresponding input button 220 is actuated, the useris returned to a home screen, such as, for example, information modehome screen 300 (FIG. 3A). In another embodiment, the user may bereturned to a menu or submenu that enabled the user to navigate to thetimeline graph 400 screen. In certain embodiments, if the user navigatesaway from the timeline graph 400 screen and later wants to return to thetimeline graph 400 screen, a remember function may be utilized whichreturns the user to the specific time period represented by the timelinegraph 400 that the user was viewing before exiting the timeline graph400 display screen. In certain embodiments, the remember function may beused for each display screen of the user interface of the analytemonitoring device 200.

FIG. 4B illustrates a display screen showing a timeline graph 460according to certain embodiments of the present disclosure. As withtimeline graph 400, timeline graph 460 includes a graph line 310 thatrepresents continuous glucose readings received over a user selectableperiod of time 410. The graph line 310 may also include a plurality ofanalyte data icons 465 to indicate the actual analyte level data valuesmeasured by sensor 101 and transmitted to analyte monitoring device 200(FIG. 2A) over the displayed period of time. In addition to analyte dataicons 465, one or more alarm notification icons 470 and/or eventnotification icons 318 (FIG. 4A) may also be displayed on or near thegraph line 310 to indicate that an alarm notification was issued overthe measured period of time or that the user participated in aparticular event. In certain embodiments, the user may acquireadditional information regarding the alarm or event such as analytelevels, insulin bolus administered, meal intake details and activitiesand the like by selecting one of the notification icons 470. In thismanner, a user can obtain current, retrospective, and/or historicstatistical information surrounding each notification icon 470 displayedon the timeline graph 460.

In certain embodiments, a softkey button or touch enabled area on thedisplay enables the user to access the additional information byhighlighting or otherwise actuating the notification icon 470. Whenactuated, the user is able to access detailed information about theparticular notification, such as measured glucose level, rate of change,historic data, trend information or activity information. Theinformational screen may also include summary information for a numberof similar types of events such as hyperglycemic events, hypoglycemicevents, rapidly rising glucose events or rapidly falling glucose events.This information may also include frequency of occurrence relative tospecific periods of time or relative to other behavior or treatments.

In certain embodiments, timeline graph 460 may also include one or moreshaded portions 480 to indicate low and/or high glucose thresholdlevels. The shaded portions 480 may be color coded as selected by a userto give the user clear indication of when the monitored glucose levelsof the user were above or below predetermined threshold levels.

FIGS. 4C-4D illustrate exemplary graphs 490 and 495 that show bloodglucose levels versus time for two simulated sets of data. Simulateddata such as shown in FIGS. 4C-4D may be used in a training mode such aswill be described in more detail below. Referring to FIG. 4C, a firstset of data points 492 output on the graph 490 show simulated data for auser that applied a late meal bolus (e.g., the user did not apply thebolus until after the meal had started). As indicated on the graph 490,the late meal bolus caused the user's blood glucose value to rapidlyrise and then level off at a high amount after the late meal bolus hadbeen applied.

The second set of data points 494 shows simulated data for a user thatapplied an on-time bolus that was under-dosed (e.g., the user appliedthe bolus before the meal began but did not apply the right amount). Asa result of the on-time bolus, the user's blood glucose value did notspike when the user applied the late meal bolus as shown by the datapoints 492. However, as shown by the data points 494, the user's bloodglucose value continued to rise consistently because the bolus wasunder-dosed or the timing was mismatched with the meal absorption.

FIG. 4D illustrates the same data from FIG. 4C, however, FIG. 4Dillustrates blood glucose values in the y-axis versus the current trendor rate of change of the blood glucose values in the x-axis. As shown bythe data points 497 (corresponding to data points 492), when a late mealbolus is applied, both the blood glucose value and the rate of changerapidly escalated. Similarly, as shown by data points 499 (correspondingto data points 494) the user's blood glucose value did not ascend ashigh when an under-dosed bolus was applied on time. However, because thebolus was under-dosed or otherwise mismatched to the meal, the rate ofchange of the blood glucose was positive and the user's blood glucoselevel continued to rise.

FIG. 4F illustrates another exemplary timeline graph according toembodiments of the present disclosure. As shown, the graph depicted inFIG. 4F includes multiple graph lines 496 with each graph line 496representing analyte levels for a respective day of the week. In certainembodiments, each graph line 496 may be color coded based on a day ofthe week. In another embodiment, each graph line 496 may be color codedbased on a severity of glucose level fluctuations. In certainembodiments, a user may highlight each of the graph lines 496 using ajog wheel, touching a portion of the touch sensitive display ofactuating a softkey button having a corresponding softkey label 440 or450. When the graph line is highlighted, statistics about the selectedgraph line 496 or event data, such as blood glucose tests, may bedisplayed on the highlighted graph line. If a user does not want to vieweach graph line for each day of the week, the user may select to viewparticular days, such as weekend or weekdays. The user may then scrollbetween a graph having five graph lines 496 representing the weekdaysand a second graph having two graph lines 496 representing weekend days.Referring still to FIG. 4A-4F, in certain embodiments, alarm or alertnotifications may be triggered by more situations where sensor dataexceed thresholds 312 and 314.

FIG. 5A illustrates a method 500 for retrospectively evaluating a seriesof received glucose data values to detect an alert condition bycomparing the received glucose data values to a trigger window inembodiments of the present disclosure. In certain embodiments, when areceived analyte level exceeds a threshold level set by the user orhealthcare professional, an alarm may be output indicating that theuser's analyte level has exceeded the threshold level. However, becauseonly the most recently received glucose level is compared against thethreshold value, the user may experience undesirable glucosefluctuations without being notified of the fluctuations. For example, auser's glucose level may be increasing or decreasing rapidly but stillbe within a predetermined threshold range. Because the glucose level isstill within the predetermined threshold range, an alert condition maynot be triggered and the user is not notified of the situation.Additionally, a user may not be notified of undesirable glucosefluctuations because an analyte monitoring device was not activated toreceive (e.g. on-demand) analyte levels during the fluctuations orepisodes of interest. As a result of not being notified, the user mayhave lost the opportunity to attempt to correct or stabilize glucoselevels, such as, for example, by administering a bolus amount ofinsulin. Further, the user may have lost the opportunity to make a noteof various conditions or events (e.g. diet, exercise, state of health,medications) that may have contributed to the rapid increase or decreasein glucose levels.

Referring to FIG. 5A, the routine for retrospectively evaluating aseries of received glucose data values begins when glucose levelinformation is received by a receiver unit (502) such as, for example,receiver unit 104 (FIG. 1). In certain embodiments, the glucose levelinformation is a blood glucose value that is received from a userinitiating a blood glucose test. In another embodiment, the glucoselevel information includes a current glucose data value that wasreceived by the receiver unit 104 from a sensor 101 (FIG. 1) via atransmitter unit 102 (FIG. 1) at predetermined time periods. In yetanother embodiment, the glucose level information may be received by thereceiver unit 104 on-demand and a series of glucose data level readingsare received simultaneously.

When the glucose level information has been received, a trigger windowhaving a minimum trigger duration (504) and a maximum trigger duration(506) is defined. In certain embodiments, a trigger window is a windowof time in which available historical glucose data values receivedduring the window of time are retrospectively evaluated to determinewhich, if any, of the historical glucose data values fall outside anacceptable range defined by the trigger window with respect to a currentglucose data value (e.g. which historical glucose data values have arate of change that when compared with the current glucose data valuecause the historical glucose data value to fall outside an acceptablerate of change). If the historical glucose data values fall outside theacceptable range defined by the trigger window, an alert notification isoutput, such as an alert screen or audible alarm, to alert the user of apossible ongoing rapid increase or decrease in glucose levels.

In certain embodiments, the minimum trigger duration defines a mostrecent point in time in the past (e.g. 15 minutes before the currentglucose data value is received) in which available historical glucosedata values will be compared to the threshold values of the triggerwindow. The maximum trigger duration defines a most distant point intime in the past (e.g. two hours before the current glucose level isreceived) that historical glucose data levels will be compared to thethreshold values of the trigger window. In certain embodiments, theminimum trigger duration and the maximum trigger duration are set by auser or a healthcare provider using, for example, a display screen andtimeframe selection items such as described herein. For example, a useror healthcare provider may navigate to a minimum trigger duration andmaximum trigger duration display screen and have the option to select atime period (e.g. 15 minutes, 2 hours etc.) of the minimum triggerduration and the maximum trigger duration.

When the minimum trigger duration and the maximum trigger duration havebeen defined, an acceptable range of glucose values is defined (508) bythe user or healthcare provider. In certain embodiments, the acceptablerange of glucose values between the minimum trigger duration and themaximum trigger duration are scaled such that all acceptable glucosedata values in the trigger window fall within a particular mg/dL perunit of time when compared to the current glucose data value level. Forexample, once the user has set the minimum trigger duration and themaximum trigger duration, the user may also select an acceptable rangeof the trigger window represented as mg/dL per unit of time, such as,for example, 100 mg/dL per hour. In certain embodiments, both thenumerical value of the mg/dL (e.g. 100) as well as the unit of time(e.g. one hour) may be selected by the user or healthcare provider.

Once the trigger window and the acceptable range have been established,available historical glucose data values are compared to the thresholdvalues shown by the trigger window to determine which, if any, of thehistorical glucose data values fall outside the established acceptablerange (510). As will be explained in greater detail below, the triggerwindow is created with respect to the most current glucose data value.Thus, as retrospective comparisons are made between the current glucosedata value and the available historical glucose data values and thetrigger window, current rapid rises or decreases in glucose levels maybe more readily detected.

FIG. 5B illustrates a graph 511 in which a trigger window 512 is definedwith respect to a current glucose data value 513 in embodiments of thepresent disclosure. As discussed above, the bounds of the trigger window512 are defined by the minimum trigger duration 515 and the maximumtrigger duration 516. As shown in FIG. 5B, the minimum trigger duration515 is set approximately fifteen minutes prior to when the most currentglucose data value 513 is received. The maximum trigger duration 516 isset approximately two hours prior to when the most current glucose datavalue 513 is received. Thus, when determining which of the historicalglucose levels 514 fall outside of the threshold values established bythe trigger window 512, comparisons will not be made for historicalglucose data values that are received after the maximum trigger duration516 and before the minimum trigger duration 515. For example, if ahistorical glucose data value was received two hours and five minutesprior to the current glucose data value 513, that particular historicalglucose data value will not be compared against the threshold valuesestablished by the trigger window 512 because that particular historicaldata value does not fall within the defined trigger window 512timeframe.

The trigger window 512 also shows an acceptable range or rate of changeof glucose values as the trigger window progresses from the minimumtrigger duration 515 to the maximum trigger duration 516. The acceptablerange of glucose values between the minimum trigger duration 515 and themaximum trigger duration 516 is scaled such that all acceptable glucosevalues in the trigger window fall within a particular mg/dL per unit oftime when compared to the current glucose level 513.

For example, and as shown in FIG. 5B, the acceptable rate of changedefined by the threshold values of the trigger window 512 is a rate ofchange that is within 100 mg/dL per hour from the current glucose value513. Thus, for a historical glucose data value to fall within theacceptable range defined by the trigger window 512, the rate of changefrom the historical glucose data value to the current glucose value mustbe less than 100 mg/dL per hour. Continuing with the example, as shownin the graph 511, the current glucose data value that was received at8:10 PM is approximately 200 mg/dL. Thus, a historical glucose datavalue that was received at 7:10 PM and compared against the triggerwindow must be no lower than 100 mg/dL and no higher than 300 mg/dL.Because the historical glucose data value received at 7:10 PM fallswithin the range defined by the trigger window, a processor of theanalyte monitoring device 200 determines that no significant rate ofchange has occurred between that particular historical glucose datavalue and the current glucose data value 513. As shown in the graph 511,none of the historical glucose data values fall outside the triggerwindow 512. Thus, it can be determined by the processor that the user isnot experiencing or has not experienced an episode of rapidly increasingor decreasing glucose levels. Although a rate of change of 100 mg/dL perhour was specifically mentioned, it is contemplated that various ratesof change per unit of time may be used, such as, for example, 5 mg/dLper 15 minutes, 10 mg/dL per 20 minutes etc.

FIG. 5C illustrates a method 520 for retrospectively evaluating a seriesof received glucose data values to detect an alert condition bycomparing the received glucose data values to a trigger window accordingto embodiments of the present disclosure. The routine forretrospectively evaluating a series of received glucose data values todetect an alert condition begins when glucose level information isreceived by a receiver (521) such as, for example, receiver unit 104(FIG. 1). In certain embodiments, the glucose level information may beobtained by a sensor such as sensor 101 (FIG. 1) and stored in thetransmitter unit 102 (FIG. 1) until the transmitter unit 102 receives arequest from the receiver unit 104 to transmit the glucose levelinformation to the receiver unit 104. In such embodiments, the glucoselevel information may contain at least a current glucose data value andat least one historical glucose data value. In another embodiment, thetransmitter unit 102 may be configured to transmit the glucose levelinformation to the receiver 104 at predetermined time intervals. In suchembodiments, the most recently received glucose data value is designatedas the current glucose data value.

When the glucose level information has been received, a trigger windowis defined having a minimum trigger duration (522) and a maximum triggerduration (523). Once the minimum trigger duration and the maximumtrigger duration have been defined, an acceptable range of glucosevalues is defined (524) with respect to the most recent or currentglucose data value. As discussed above, each of the minimum triggerduration, the maximum trigger duration and the acceptable range may bedefined or selected by a user or healthcare provider. The historicglucose data values are then compared by a processor to the thresholdvalues established by the trigger window to determine which, if any, ofthe historic glucose data values fall outside the established acceptablerange (525). If it is determined that one or more historical glucosedata values fall outside the established range defined by the triggerwindow, this could indicate that an unacceptable glucose fluctuation isin progress.

If it is determined by the processor that one or more historic glucosedata values fall outside the established acceptable range, the processorof the receiver unit 104 records the occurrence of the condition (526).In certain embodiments, recording the occurrence of the conditionincludes placing an icon on a graph, such as a timeline graph 400 (FIG.4A). In other embodiments, the receiver unit 104 may be configured togenerate a graph similar to the graph 531 of FIG. 5D and the graph isoutput on a display screen of the receiver unit 104. In certainembodiments, when a condition is detected, an alarm and/or an alertscreen is output on the receiver unit 104 to notify the user of thedetected condition. Additionally, when the user is notified of thecondition, the user may be prompted by the alert screen to recorddetails of events (e.g., diet, activity, medication etc.) that may havecaused the fluctuation to occur.

In certain embodiments, a processor the receiver unit 104 is configuredto automatically associate event information entered by a user (e.g.exercise periods, meals etc.) or other automatically detected events(e.g., hypoglycemia, hyperglycemia, rapid glucose increases, rapidglucose decreases, glucose threshold alarms, impending glucose thresholdalarms) to the detected episode if the event falls within a matchingwindow relative to the episode. For example, if it is determined, basedon a historical glucose data value falling outside the acceptable range,that an episode of increased blood glucose levels is occurring, an eventhistory log created by the user may be evaluated to determine if aparticular event occurred within a predetermined time range prior to thestart of the episode that may have caused the current increase inglucose values. In certain embodiments, the matching window may be anytimeframe selected by a user or healthcare provider.

FIG. 5D is a graph 531 illustrating a detected rise in glucose levelsthat is currently occurring according to embodiments of the presentdisclosure. The graph 531 includes a trigger window 532 defined by aminimum trigger duration 533 and a maximum trigger duration 534. Asdiscussed above, the trigger window 532 shows the acceptable range ofglucose values between the minimum trigger duration 533 and the maximumtrigger duration 534. Graph 531 also shows a plurality of glucose datavalues including a current glucose data value 535, a second mostrecently received glucose data value 536, and a plurality of otherhistorical glucose data values 537.

Unlike the graph 511 of FIG. 5B, some of the historical glucose datavalues 537 fall outside of the trigger window 532. When at least one ofthe historical glucose data values fall outside the threshold set by thetrigger window 532, an episode of increased or decreased glucose levelsis likely ongoing or has occurred in the past. If an ongoing episode isdetected, a processor of the receiver unit 104 is configured todetermine the start of the episode. To determine a start of an episode,the historical glucose data values 537 are evaluated retrospectivelystarting from the second most recently received glucose data value 536and moving back in time. Each historical glucose data value 537 isevaluated in turn to determine which historical glucose data value 537is closest to the threshold level defined by the trigger window 532 interms of time but farthest away from the threshold level defined by thetrigger window 532 in terms of a glucose level relative to historicalglucose data values immediately before and/or after the historicalglucose data value currently being evaluated.

For example, as shown on the graph 531, the historical glucose datavalue 538 is indicated as the start of the episode because thehistorical glucose data value 538 is closest to the threshold leveldefined by the trigger window 532 in terms of time but has a lowerglucose value than the previously received historical glucose datavalue. Once the start of the episode is identified, it can be determinedhow long the current episode has been ongoing. In the graph 531, theepisode was determined to start when the historical glucose data value538 was received at 7:50 PM. Because the current glucose data value wasreceived at approximately 8:20 PM, the episode duration, indicated byline 540, has been occurring for 30 minutes.

In certain embodiments, when the episode duration has been determined, alocal minimum rate of change and a local maximum rate of change for theepisode duration may be determined by comparing each of the historicaldata values with each of the other historical data values to determinethe smallest rate of change between the two values. Such information maybe useful to determine which events or activities by the user, if any,had the least amount of significance to the occurrence of the episode.For example, if the user ate a meal twenty minutes prior to theoccurrence of the smallest rate of change between two of the values, itcan be determined that the meal did not affect the user's glucose levelin that particular episode.

The local maximum rate of change is the largest rate of change betweenany two values during the occurrence of the episode. As shown in thegraph 531, the local maximum rate of change in the episode 540 occurredbetween the current glucose data value 535 and the second most recentlyreceived glucose data value 536. Because the local maximum rate ofchange is recorded, a user may use this information to determine whichevents, if any, may or may not have contributed to jump in glucosevalues between these two readings.

Also shown on graph 531 is a matching window line 541 that represents amatching window time period. In certain embodiments, the matching windowtime period is a time period that starts at a predetermined amount oftime prior to the detected start of the episode and ends when theepisode ends. For example, as depicted in FIG. 5D, the matching windowtime period starts approximately 30 minutes prior to the start of thedetected episode and ends at the same time as the episode. Although a 30minute time period is specifically shown, it is contemplated thatvarious other time periods may be selected by a user or healthcareprovider.

As discussed above, the matching window may be used to automaticallyassociate events, that occurred during the matching window time period,to the episode to enable a user or healthcare provider to ascertainwhich events may have caused, or were at least related to, the rapidincrease or decrease in glucose levels. Such examples include othersignificant increases or decreases in glucose, episodes of high or lowglucose, glucose alarm events, meal times, exercise periods, and thelike. For example, if a user recorded an event, such as, for example, ameal at approximately 7:30 PM and the episode started at 7:50 PM, it maybe determined by the user or healthcare provider that the particularmeal eaten by the user was at least a factor in the episode starting.Thus, the user may take steps to prevent future episodes from occurringby avoiding similar foods.

FIG. 5E illustrates a method 550 for detecting an alert condition in aglucose monitoring system by retrospectively comparing historicalglucose data values to each of the other historical data values withrespect to a trigger window according to embodiments of the presentdisclosure. The routine for detecting an alert condition in a glucosemonitoring system begins when glucose level information is received by areceiver (551) such as, for example, receiver unit 104 (FIG. 1). Incertain embodiments, the glucose level information may be obtained by asensor such as sensor 101 (FIG. 1) and stored in the transmitter unit102 (FIG. 1) until the transmitter unit 102 receives a request from thereceiver unit 104 to transmit the glucose level information to thereceiver unit 104. When the glucose level information is transmitted inthis manner, an entire series of glucose data values may be transmittedby the transmitter unit 102 and received by the receiver unit 104. Theseries of glucose data values includes at least a current or most recentglucose data value and at least one historical glucose data value. Inanother embodiment, the transmitter unit 102 is configured to transmitthe glucose level information to the receiver 104 at predetermined timeintervals and the most recently received glucose data value is set asthe current glucose data value.

When the glucose level information has been received, a trigger windowis defined having a minimum trigger duration (552) and a maximum triggerduration (553) such as described above. When the minimum triggerduration and the maximum trigger duration have been defined, anacceptable range of glucose values is also defined (554) with respect tothe most recent or current glucose data value. As discussed above, eachof the minimum trigger duration, the maximum trigger duration and theacceptable range may be defined or selected by a user or healthcareprovider. A processor of the receiver unit 104 compares the historicglucose data values to the trigger window to determine which, if any, ofthe historic glucose data values fall outside the established acceptablerange (555).

If it is determined that one or more historic glucose data values falloutside of the established acceptable range (556), the receiver unit 104records the occurrence of the condition (557). In certain embodiments,recording the occurrence of the condition includes placing an icon on agraph, such as a timeline graph 400 (FIG. 4A). In other embodiments, theprocessor of the receiver unit 104 may be configured to generate a graphsimilar to the graph 531 of FIG. 5D and the graph is output on a displayof the receiver unit 104. In certain embodiments, when a condition isdetected, the receiver unit 104 may be configured to output an alarm oralert notification screen to notify the user of the detected condition.Additionally, when the user is notified of the condition, the user maybe prompted to enter events (e.g., diet, activity, medication etc.) thatmay have caused the fluctuation to occur.

However, if it is determined that an episode is not currently ongoing(556), a second most recently received glucose data value is selected(558) and each of the historical data values are evaluated against thetrigger window with respect to the second most recently received glucosedata value (555). If it is determined that one or more historic glucosedata values fall outside the established acceptable range (556) withrespect to the second most recently received glucose data value, aprocessor of the receiver unit 104 records the occurrence of thecondition (557) such as was described above. It should be noted, that ifthe second most recently received glucose data value is used to evaluatethe rest of the historical glucose data values, the trigger window thatwas established based on the current glucose data value is used in theevaluation relative to the second most recently received glucose datavalue. Thus, the minimum trigger duration, the maximum trigger durationand the acceptable range of glucose values of the trigger window remainunchanged.

FIG. 5F illustrates a graph 560 for retrospectively comparing a secondmost recently received glucose data value to historical glucose datavalues with respect to a trigger window in embodiments of the presentdisclosure. As with the other graphs described above, graph 560 includesa trigger window 561 defined by a minimum trigger duration 562 and amaximum trigger duration 563. The trigger window 561 shows theacceptable range of glucose values between the minimum trigger duration562 and the maximum trigger duration 563. Graph 560 also shows aplurality of glucose data values including a current glucose data value564, a second most recently received glucose data value 565, and aplurality of other historical glucose data values 566. As discussedabove, a processor of the receiver unit 104 compares the historicalglucose data values 566 against threshold values defined by the triggerwindow 561 to determine if any of the historical glucose data valuesfall outside the threshold values defined by the trigger window 561 withrespect to the second most recently received glucose data value 565.

Although not shown on the graph 560, when each of the historical glucosedata values 566 were compared to the threshold values defined by thetrigger window 561 with respect to the current glucose data value 564,none of the historical glucose data values fell outside the threshold.As a result, the second most recently received glucose data value 565 isselected as a new current glucose data value and the trigger window iseffectively “moved back” to the location shown on the graph 560.Although the trigger window has been effectively “moved back”, theparameters of the minimum trigger duration 562, the maximum triggerduration 563 and the acceptable range of glucose values remain constant.Thus the same parameters that were used to evaluate the historicalglucose data values with respect to the current glucose data value 564are used to evaluate the historical glucose data values with respect tothe second most recently received glucose data value 565.

For example, if the minimum trigger duration 562 was set as 15 minutesprior to the current glucose data value 564 being received and themaximum trigger duration 563 was set as 2 hours prior to the currentglucose data value being received, these same values are used when thesecond most recently received glucose data value 565 is analyzed inplace of the current glucose data value 564. Thus, the minimum triggerduration 562 is set 15 minutes prior to when the second most recentlyreceived glucose data value 565 was received and the maximum triggerduration 563 is set as 2 hours prior to when the second most recentlyreceived glucose data value 565 was received.

As shown in the graph 560, once the trigger window 561 has been movedback, some of the historical glucose data values 566 now fall outsidethe threshold range defined by the trigger window 561. As a result, itmay be determined that an episode, such as rapidly increasing glucoselevels, occurred in the past and is either still occurring or is nolonger occurring. Regardless of whether the episode is still occurring,a processor of the receiver unit 104 is configured to determine thestart of the episode. When determining a start of an episode, thehistorical glucose data values 566 are evaluated retrospectivelystarting from the third most current glucose data value and moving backin time. Each historical glucose data value 566 is evaluated in turn todetermine which historical glucose data value 566 is closest to thethreshold defined by the trigger window 561 in terms of time butfarthest away from the threshold defined by the trigger window 561 interms of a glucose level relative to historical glucose data valuesimmediately before and/or after the historical glucose data valuecurrently being evaluated.

As shown in FIG. 5F, historical glucose data value 568 is the firsthistorical glucose data value to fall outside of the threshold definedby the trigger window 561. However, before start of the episode is setat this particular point, the previously received historical glucosedata value indicated by 569 is evaluated with respect to the historicalglucose data value 568 to determine which historical glucose data valuehas a lower (or higher in cases of decreasing glucose levels) glucoselevel. If a previous historical glucose data value has a glucose levelthat is equal to or lower than the historical glucose data value that iscurrently being evaluated, additional subsequent historical glucose datavalues are evaluated. For example and as shown in the graph 560, becausethe historical glucose data value 569 has a lower glucose level than thehistorical glucose data value 568, additional previously receivedhistorical glucose data values will be evaluated to determine the startof the episode. However, if a previously received historical glucosedata value has a glucose level that is higher than the historicalglucose data value currently being evaluated, it is determined that theepisode started with the historical glucose data value that is currentlybeing evaluated.

As discussed above, because the historical glucose data value 569 has alower glucose level than the historical glucose data value 568,additional previously received historical glucose data values will beevaluated to determine the start of the episode. As shown on the graph560, as additional previously received glucose data values areevaluated, it is determined that the historical glucose data value 567is where the episode began. In certain embodiments, this determinationis made because the historical glucose data value 567 is closest to thetrigger window 561 in terms of time and has an equal or substantiallyequal glucose value than the subsequent historical glucose data value569. Further, the historical glucose data value that was receivedprevious to the historical glucose data value 567 is within the triggerwindow 561 and therefore is not a part of the current episode.

Once the start of the episode is identified, it can be determined howlong the current episode has been ongoing. In the example shown in FIG.5F, the episode was determined to start when the historical glucose datavalue 567 was received at 7:50 PM. To determine the end of the episode,the second most recently received glucose data value 565 is comparedagainst the current glucose data value 564 to determine if the currentepisode is ongoing. Because the subsequently received glucose data value(e.g., the current glucose data value 564) is equal to or greater than(or equal to or lower than in cases of decreasing blood glucose levels)the previously received glucose data value (e.g., the second mostrecently received glucose data value 565) it is determined that theepisode is ongoing as shown by episode duration line 570. Thus theepisode started at 7:50 PM and is ongoing through at least 9:20 PM.However, if the subsequently received glucose data value (e.g., thecurrent glucose data value 564) is less than (or greater than in casesof decreasing blood glucose levels) the previously received glucose datavalue (e.g., the second most recently received glucose data value 565)the episode ended when the previously received glucose data value wasreceived.

When the episode duration has been determined, a local minimum rate ofchange and a local maximum rate of change for the episode duration maybe determined by comparing each of the historical data values with eachof the other historical data values. As shown in the graph 560, themaximum rate of change in the episode occurred between the historicglucose data value 568 and the subsequently received historic glucosedata value. Because the local maximum rate of change is recorded, a usermay use this information to determine which events, if any, may or maynot have contributed to jump in glucose values between these tworeadings as well as the severity of each rise.

Also shown on graph 560 is a matching window line 571 that represents amatching window time period. In certain embodiments, the matching windowtime period is a time period that starts at a predetermined amount oftime prior to the start of the episode and ends when the episode ends.The matching window may be used to automatically associate events, thatoccurred during the matching window time period, to the episode toenable a user or healthcare provider to ascertain which events may havecaused, or were at least related to, the rapid increase or decrease inglucose levels.

FIG. 5G illustrates a graph 580 in which a trigger window is definedwith respect to a current blood glucose data value in embodiments of thepresent disclosure. In certain embodiments, graph 580 may be used in atest strip monitoring device to compare a newly acquired blood glucosereading to a previously received blood glucose reading. Although bloodglucose readings are used instead of continuous glucose readings, themethodology is similar to the methodologies described above. As shown inFIG. 5G, graph 580 includes a trigger window 581 defined by a minimumtrigger duration 582 and a maximum trigger duration 583. The triggerwindow 581 shows the acceptable range of glucose values between theminimum trigger duration 582 and the maximum trigger duration 583. Graph580 also shows a plurality of blood glucose data values including acurrent blood glucose data value 584 and a previously received bloodglucose data value 585. Although only two values are shown, it iscontemplated that additional blood glucose values may be received andplotted on the graph. As with the historical glucose data valuesdiscussed above, the previously received blood glucose data value 585 iscompared against threshold levels defined by the trigger window 581 todetermine if the previously received blood glucose data value fallsoutside the threshold range defined by the trigger window 581 withrespect to the current blood glucose data value 584.

In certain embodiments, a graph, such as for example graph 460 (FIG. 4B)may be output on the display 210 (FIG. 2A) of the analyte monitoringdevice 200 showing the detected rises and falls and highs and lows ofreceived blood glucose data values based on a set of detectionparameters. In certain embodiments, the set of detection parameters usedfor the graph may be similar to the parameters used to define a triggerwindow and/or an outer limit range associated with the trigger window.In certain embodiments an indicator, such as, for example, a triangle orrectangle, may be displayed on the graph that links or surrounds theblood glucose data values of a particular episode that was detectedbased on the detection parameters. In an embodiment, the indicators arecolor coded based on severity of the episode, duration of the episode,extreme high values of glucose data values in the episode, and/orextreme low values of glucose data values in the episode.

Referring back to FIG. 5G, because the previously received blood glucosedata value 585 falls outside of the threshold level defined by thetrigger window 581, a processor of the receiver unit 104 (FIG. 1) candetermine that a rapid increase or decrease in blood glucose levels isongoing. As a result, the processor of the receiver unit 104 may recordthe occurrence of the condition such as described above with respect toFIG. 5C.

In certain embodiments, if an ongoing episode is detected, the processorof the receiver unit 104 is configured to determine the start of theepisode. Although there are only two blood glucose levels shown on thegraph 580, the start of the episode is determined in the same manner aswas described above with respect to FIG. 5D. As shown, the previouslyreceived blood glucose data value 585 is determined to be the bloodglucose value at which the current episode started. Once the start ofthe episode is identified, it can be determined how long the currentepisode has been ongoing. As shown in FIG. 5G, the episode wasdetermined to start when the first blood glucose data value 585 wasreceived at approximately 8:00 PM and is continually ongoing up until atleast approximately 9:20 PM when the current blood glucose value isreceived. Thus, the episode duration, indicated by line 586, has beenoccurring for 1 hour and 20 minutes.

In certain embodiments, when the episode duration has been determined, alocal minimum rate of change and a local maximum rate of change for theepisode duration may be determined such as was described above. Suchinformation may be useful to determine which events or activitiesinitiated by the user, if any, had the least amount of significance orgreatest amount of significance to the occurrence of the episode.

Also shown on graph 580 is a matching window line 587 that represents amatching window time period. In certain embodiments, the matching windowtime period is a time period that starts at a predetermined amount oftime prior to the episode starting and ends when the episode ends. Forexample, as depicted in FIG. 5G, the matching window time period startsapproximately 30 minutes prior to the start of the detected episode andends at the same time as the episode. Although a 30 minute time periodis specifically shown, it is contemplated that various other timeperiods may be selected and used. As discussed above, the matchingwindow may be used to automatically associate events, that occurredduring the matching window time period, to the episode to enable a useror healthcare provider to ascertain which events may have caused, orwere at least related to, the rapid increase or decrease in bloodglucose levels.

FIG. 5H is a graph 589 illustrating episode detection in which allglucose data values associated with the episode fall within an outerlimit range according to embodiments of the present disclosure. Thegraph 589 includes a trigger window 590 defined by a minimum triggerduration 591 and a maximum trigger duration 592. As discussed above, thetrigger window 590 shows the acceptable range of glucose values betweenthe minimum trigger duration 591 and the maximum trigger duration 592.Also shown on graph 589 is an outer limit 597 range. As will bedescribed in greater detail below, when an outer limit range is used,only rise and fall episodes whose extreme glucose data values arecontained entirely within the outer limit range 597 are detected. Anyglucose data values of an episode that fall outside of the outer limitrange 597 are ignored. In such instances, an episode associated with theextreme glucose data value is also ignored. Graph 589 also shows aplurality of glucose data values including a current glucose data value593, a second most recently received glucose data value 594, and aplurality of additional historical glucose data values 595.

As shown in the graph 589, some of the historical glucose data values595 fall outside of the trigger window 590 but within the outer limitrange 597. As described above with respect to FIG. 5D, when at least oneof the historical glucose data values fall outside the threshold set bythe trigger window 590, an episode of increased or decreased glucoselevels is likely ongoing or has occurred in the past. If an ongoingepisode is detected, a processor of the receiver unit 104 is configuredto determine the start of the episode. To determine a start of anepisode, the historical glucose data values 595 are evaluatedretrospectively starting from the second most recently received glucosedata value 594 and moving back in time. Each historical glucose datavalue 595 is evaluated in turn to determine which historical glucosedata value 595 is closest to the threshold level defined by the triggerwindow 590 in terms of time but farthest away from the threshold leveldefined by the trigger window 590 in terms of a glucose level relativeto historical glucose data values 595 immediately before and/or afterthe historical glucose data value currently being evaluated.

For example, as shown on the graph 589, the historical glucose datavalue 596 is indicated as the start of the episode because thehistorical glucose data value 596 is closest to the threshold leveldefined by the trigger window 590 in terms of time but has a lowerglucose value than the previously received historical glucose datavalue. However, should any historical glucose data values 595 falloutside of the outer limit range 597, the entire episode is ignored.

Although some historical glucose data values associated with an episodemay fall outside of the outer limit range 597 and therefore the episodeis not detected, in certain embodiments, a user or health care providermay adjust the trigger window parameters and/or the parametersassociated with the outer limit range 597 so that in subsequent episodedetections, the historical glucose data values that previously felloutside of the outer limit range 597, as well as the episode associatedwith historical glucose data value, is detected and may be evaluatedand/or displayed. Such embodiments enable a user or health care providerto closely examine a number of episodes having varying degrees ofseverity.

In certain embodiments the parameters associated with the trigger windowand the outer limit range 597 may be a set of predefined parameters andepisode detection is applied for each predefined sets. For example, iften sets of predefined parameters (e.g., minimum trigger duration,maximum trigger duration, acceptable glucose range etc.) are defined,episodes detection is performed on each set of parameters. In this way aspectrum of episodes are found and may be evaluated by a user or healthcare provider. Using sets of parameters such as described above enableidentification of episodes having varying intensities and times. Forexample, long, slow episodes could be found with one set of parameters,while another set of parameters would detect short, fast episodes. Asdescribed above, the acceptable glucose range might be a band of valuesthat fall within the outer limit range (e.g., the glucose data valuesthat increased between 100 and 120 mg/dL per hour). Additionally, asingle set of parameters may be further analyzed to determine thefrequency at which episodes corresponding to the selected parametersoccur. For example, short, fast episodes may be found to be occurringevery day at a given time. Once the frequency of the episode isidentified, a user or health care provider may take steps to identifywhat activities may be contributing to the frequency of the episode.

Once the episode has been detected and the start of the episode isidentified (e.g., all of the historical glucose data values associatedwith the episode fall within the outer limit range 597), a time periodof the episode can be determined. In the graph 589, the episode isdetermined to have started when the historical glucose data value 596was received at 7:50 PM. Because the current glucose data value wasreceived at approximately 8:20 PM, the episode duration, indicated byline 598, has been occurring for 30 minutes.

In certain embodiments, when an episode duration has been determined, alocal minimum rate of change and a local maximum rate of change for theepisode duration may be determined by comparing each of the historicaldata values with each of the other historical data values to determinethe smallest rate of change between the two values. Such information maybe useful to determine which events or activities by the user, if any,had the least amount of significance to the occurrence of the episode.For example, if the user ate a meal twenty minutes prior to theoccurrence of the smallest rate of change between two of the values, itcan be determined that the meal did not affect the user's glucose levelin that particular episode.

The local maximum rate of change is the largest rate of change betweenany two values that fall within the outer limit range 597 during theoccurrence of the episode. As shown in the graph 589, the local maximumrate of change in the episode 598 occurred between the current glucosedata value 593 and the second most recently received glucose data value594. Because the local maximum rate of change is recorded, a user mayuse this information to determine which events, if any, may or may nothave contributed to jump in glucose values between these two readings.

Also shown on graph 589 is a matching window line 599 that represents amatching window time period. In certain embodiments, the matching windowtime period is a time period that starts at a predetermined amount oftime prior to the detected start of the episode and ends when theepisode ends. For example, as depicted in FIG. 5H, the matching windowtime period starts approximately 30 minutes prior to the start of thedetected episode and ends at the same time as the episode. Although a 30minute time period is specifically shown, it is contemplated thatvarious other time periods may be selected by a user or healthcareprovider.

As discussed above, the matching window may be used to automaticallyassociate events, that occurred during the matching window time period,to the episode to enable a user or healthcare provider to ascertainwhich events may have caused, or were at least related to, the rapidincrease or decrease in glucose levels. Such examples include othersignificant increases or decreases in glucose, episodes of high or lowglucose, glucose alarm events, meal times, exercise periods, and thelike. For example, if a user recorded an event, such as, for example, ameal at approximately 7:30 PM and the episode started at 7:50 PM, it maybe determined by the user or healthcare provider that the particularmeal eaten by the user was at least a factor in the episode starting.Thus, the user may take steps to prevent future episodes from occurringby avoiding similar foods.

FIG. 6 illustrates an exemplary menu screen 600 screen type according toembodiments of the present disclosure. Although the menu screen 600shown in FIG. 6 is specific to a main menu, the user interface includesa number of menus and submenus corresponding to various functionalitiesand display screens. As such, it will be understood that all of themenus, functions, and display screens may be navigated in a way similarto the way described with reference to FIG. 6.

In certain embodiments, menu screen 600 may include a plurality of menuitems. Specific examples include an alarm settings menu item, a reportsmenu item, an add events menu item, a status menu item and a settingsmenu item to name just a few. Although specific menu items in particularorders are shown and discussed, it is contemplated that a user mayselect various menu items and select the order of the menu itemsdisplayed in the menu screen 600. As stated above, each menu item mayhave corresponding submenus, display screens or functions that enable auser to customize the analyte monitoring device 200 for personal use.The menu screen may also contain menu items for clearing user settingsand erasing user history. When implemented, the menu items for clearinguser settings and erasing user histories may be password protected toprevent a user from unintentionally deleting the data on the analytemonitoring device 200.

In certain embodiments, the menu screen 600 is rendered on the display210 in response to a user actuating an input button 220 (FIG. 2A).Referring to FIG. 3A above, to display the menu screen, the softkeybutton actuated is the input button 220 that corresponds to softkeybutton label 344 labeled “Menu.” Although a specific softkey label 344and corresponding input button 220 are mentioned, it is contemplatedthat the menu screen 600 may be accessed by actuating a pre-programmedbutton or a touch sensitive portion of the display 210 (FIG. 2A).

In certain embodiments, menu screen 600 includes a title portion 610indicating the name of the current menu or submenu the user hasnavigated to as well as a list of menu items 640 available for theparticular menu. For example, the list of menu items 640 shown in FIG. 6includes a “Connect to Sensor” menu item, an “Alarms” menu item, a“Reports” menu item, and an “Add Event” menu item. A scroll indicator620 is shown to indicate additional menu items are on the list but arenot currently visible on the display 210. Such examples include a“Status” menu item, a “Settings” menu item and a “Manual Calibration”menu item. The scroll indicator 620 may also have a position indicator625 to indicate a position on the menu. For example, as shown in FIG. 6,the position indicator 625 is located at the top of the scroll indicator620. This shows that a selection indicator 630 is at the first menu itemof the menu screen 600. As the selection indicator moves to variousitems in the list, the position indicator 625 moves along the scrollindicator 620 to indicate how far down the list of menu items the userhas navigated. In one aspect, a processor of the analyte monitoringdevice 200 causes each of the menu items to change from a first color toa second color when the menu item is selected. For example, a first menuitem that is selected may be a first color, while the remaining menuitems are displayed in a second color.

In certain embodiments, the menu screen 600 is navigable using ascrolling device, such as jog wheel 230 (FIG. 2C), or by actuating aninput button 220. In certain embodiments, wrap navigation may be used inwhich the user may scroll from the first item in the list directly tothe last item in the list and vice versa. As the jog wheel 230 isactuated, the selection indicator 630 moves from one menu item to anext, or subsequent, menu item. For example, if the “Sensor” menu itemis currently selected by the selection indicator 630, as the jog wheel230 is actuated in a downward motion, the selection indicator 630 movesto the “Alarms” menu item.

When the selection indicator 630 highlights a desired menu item, a useractuates a softkey button having a corresponding softkey label such as,for example, right softkey label 650 or left softkey label 660.Continuing with the example, the right softkey label 650 may be labeled“Select” for selection of the currently highlighted menu item and theleft softkey label 660 may be labeled “Home” which returns a user to thehome screen, such as, for example, home screen 300. Other softkey labelsmay be used based on the various menu states of the menu. Such examplesinclude softkey labels for “Next”, “Done”, “Accept”, and “Cancel” toname a few. In certain embodiments, when a particular menu item ishighlighted, selection of the menu item may be made by inwardlydepressing the jog wheel 230. In yet other embodiments, the selection ofthe highlighted menu item may be made using a touch sensitive portion ofthe display 210.

When a selection of the menu item is made, a unique display screen isoutput on the display 210. In certain embodiments, the display screen isspecific to each of the menu items 640. In certain embodiments, somemenus have multiple status screens that are linearly arranged. Thus,data and status information may be viewed simply by actuating the jogwheel 230 or a softkey button having a corresponding softkey label(e.g., “Next”) used for advancing through the various status screens ofthe menu. In certain embodiments, the system “remembers” the order inwhich the display screens were output on the display 210. Thus, a usermay return to a previously viewed display screen by actuating a softkeybutton that functions as a “back” button. As such, previously vieweddisplay screens may be output on the display 210 in reverse order.

In certain embodiments, each of the menu screens contain a number ofmenu items. Each menu item may have submenus having submenu items thatcorrespond to various display screens of the analyte monitoring device200. Although the menu items 640 in the menu screen 600 may be arrangedin default settings, it is contemplated that a user may manually selectvarious menu items 640 and display screens that are output on the mainmenu screen 600. As particular menus are accessed and as functionscorresponding to the menus are utilized, the position of thecorresponding menu items 640 in the menu screen 600 may move up or downthe menu screen 600 based on frequency of use. For example, if the“Alarms” menu item 640 is selected more frequently than the “Connect toSensor” menu item 640, the “Alarms” menu item 640 would be the firstmenu item 640 in the menu screen 600.

In certain embodiments, the menu screen 600 contains at least sevenvarious submenus and/or display screens with each submenu and displayscreen having specific features or functionalities. It will beunderstood that navigation and selection of items on the varioussubmenus and display screens described below may be accomplished in asimilar manner as described above with respect to FIG. 6.

Connect to Sensor

The “Connect to Sensor” menu item enables a user to wirelessly connectto a sensor, such as sensor 101 (FIG. 1) described above and/or allowsthe user to ascertain whether the analyte monitoring device 200 (FIG.2A) is connected to the correct transmitter and/or sensor (e.g., thetransmitter and/or sensor of the user of the analyte monitoring device200) before initiating transmitter communication and reception ofanalyte readings from the sensor. In certain embodiments, when the“Connect to Sensor” menu item is selected on the menu screen 600, themenu screen 600 linearly progresses to a sensor submenu 700 as shown inFIG. 7. The sensor submenu 700 includes a title portion 710 indicatingthe name of the submenu (e.g., Sensor Menu) as well as a list of menuitems 740 available in the Sensor Menu. For example, the Sensor Menuincludes a “Connect to Sensor” menu item and a “Calibration BG” menuitem. In certain embodiments, the sensor submenu 700 also includes ascroll indicator 720 having a position indicator 725 that indicates aposition of a selection indicator 730. In certain embodiments, thescroll indicator 720 and position indicator 725 are output on thedisplay 210 only when the number of menu items displayed on the menuexceed a predetermined number (e.g., 4). For example, if the menu screenhas three menu items, the scroll and position indicators are not outputon the menu screen. If the menu screen has five menu items, the scrollindicator and position indicator are output on the menu screen. Althoughthe above example is given with respect to FIG. 7, it is contemplatedthat the scroll and position indicators for each of the various menuscreens discussed herein may be displayed based on the number of menuitems in the menu screen.

Referring back to FIG. 7, when the “Calibration BG” menu item isselected (e.g., by actuating a softkey button corresponding to the“Select” softkey label 750 when the “Calibration BG” menu item ishighlighted by the selection indicator 730), a message screen is outputon the display 210 (FIG. 2A) asking a user if calibration of the sensoris desired. If the user selects the option to proceed with thecalibration, further instructions are output on the display 210. Incertain embodiments, the message screen may also provide a time periodin which the next calibration is needed and a grace period forcalibration. Thus, if the user does not want to proceed immediately withthe calibration, the user is put on notice of when the next calibrationshould occur.

When the “Connect to Sensor” menu item is selected (e.g., by actuating asoftkey button corresponding to the “Select” softkey label 750 when the“Connect to Sensor” menu item 740 is highlighted by the selectionindicator 730), an instruction screen is output on the displayinstructing a user told to hold the analyte monitoring device 200 nextto the sensor. If a sensor is detected within range of the analytemonitoring device 200, a progress alarm is output by the analytemonitoring device 200 to indicate that a connection between the sensorand the analyte monitoring device 200 was made. When the connectionbetween the analyte monitoring device 200 and the sensor is established,a message screen is output on the display 210 that prompts a user toenter in a sensor code that corresponds to a code of the actual sensorthe user is using. As with other alarms or auditory notificationsdescribed herein, the tone or sound of the progress alarm may beselected by a user. It is also contemplated that additional sounds ortones, such as music, recorded speech, and the like, may be downloaded,stored on the analyte monitoring device 200 and used as alarms.

In certain embodiments, if a connection with the sensor is notestablished within a predetermined amount of time, a second instructionscreen is output on the display 210 indicating that a connection betweenthe sensor and the analyte monitoring device 200 was not established. Anaudible alarm and/or vibration may also be output to indicate that asensor was not found by the analyte monitoring device 200. A user maynavigate away from the second instruction screen using the softkeybuttons such as input buttons 220 having corresponding softkey labels orby using secondary button 240 to return to a previous menu or displayscreen. If a connection is not established between the sensor and theanalyte monitoring device 200, a second alarm and corresponding alertscreen may be output by the analyte monitoring device 200 indicatingthat continuous glucose data from the sensor is not available. If thecontinuous glucose data is unavailable for a predetermined amount oftime (e.g. 1 hour) additional alarms and display screens may be outputon the display 210 to put the user on notice that data is not currentlybeing received by the analyte monitoring device 200. To return to menuscreen 600, a user may actuate a softkey button corresponding to the“Home” softkey label 760. Further details regarding connection to asensor and corresponding alert screens are illustrated in FIG. 26described below.

Alarm Settings

An “Alarm Settings” submenu 800 is shown in FIG. 8 according toembodiments of the present disclosure. The “Alarm Settings” submenu 800is provided to a user when the “Alarm Settings” menu item is selectedfrom the menu screen 600. In certain embodiments, the “Alarm Settings”submenu 800 includes a title portion 810 indicating the name of thesubmenu as well as a list of menu items 840 available in the submenu. Incertain embodiments, the “Alarm Settings” submenu 800 also includes ascroll indicator 820 and a position indicator 825 that indicates aposition of a selection indicator 830. The “Alarm Settings” submenuenables a user to select alarm tones, alarm volumes, frequency of alarmsas well as vibration settings for the analyte monitoring device 200. The“Alarm Settings” menu screen 800 may include menu items 840 with eachmenu item having its own functionality or display screen. For example,the additional alarm settings menu items may include an “Audio/Vibrate”item, a “Mute Alarms” menu item, a “Glucose Alarms” menu item, a “Tones”menu item, a “Snooze Setup” menu item and a “Charging Setup” menu item.Although specific titles have been used, other titles may be used toindicate similar or additional functionality with respect to alarms. Incertain embodiments, selection of a menu item 840 is made by actuating asoftkey button corresponding to the “Select” softkey label 850. Incertain embodiments, a user may return to the menu screen 600 or to homescreen 300 (FIG. 3A) by actuating a softkey button corresponding to the“Home” softkey label 860.

The “Audio/Vibrate” menu item enables a user to select various alarmsettings. These settings may include the type of alarm, for example,audio only, vibration only, or audio and vibration. In certainembodiments, the user may also select an option in which a vibratory ortactile alert trumps an audible setting for individual alarms. The“Alarm Settings” menu item may also include an option to adjust overallvolume level of the alarms of the analyte monitoring device 200. Theoverall volume level may be user selectable with options for high,medium and low.

Additionally, the “Alarm Settings” may also include volume settings forprogress tones. In certain embodiments, progress tones are sounds outputfrom the analyte monitoring device 200 to notify a user about theprogress and status of specific steps, such as, for example connectingto a sensor. The volume setting may include high, medium, low, and off.

When volume and/or vibration setting selections are made, (e.g., audioand vibration selected as the type of alarm), a sample alarm and/orvibration is output from the analyte monitoring device 200 to the user.Once selected, the user may confirm the selection by actuating a softkeybutton or by touching an area on the touch sensitive display. In certainembodiments, the user may choose a different sound and/or vibration foreach alarm. As discussed above, this setting may be depicted on a homescreen by an icon, such as audio/vibratory settings icon 332 (FIG. 3A).

FIG. 9 shows an exemplary “Mute Alarms” display screen 900 that isoutput on the display 210 (FIG. 2A) when the “Mute Alarms” menu item isselected from the “Alarm Settings” menu screen 800 (FIG. 8). The “MuteAlarms” display screen 900 includes a title portion 910 as well as an“Accept” softkey label 920. The “Mute Alarms” display screen 900presents a user with different muting options to mute alarms that areassociated with various alert conditions. For example, one alarm maycorrespond to a low battery alert condition and another alarm maycorrespond to an impending hypoglycemia condition. To mute alarms, theuser may be presented with a screen having a selectable mute durationfrom 1 hour up to 12 hours in one hour increments. If a user mutes anyof the alarms for more than 12 hours, the user may be required to turnoff each alarm one at a time. In certain embodiments, once the selectedmute time has elapsed, the alarms return to the original settings (e.g.a 1 hour setting). In certain embodiments, although some alarms aremuted, such as, for example, alarms corresponding to medium urgencyalerts described below, vibratory and onscreen text notifications maystill be output on the display 210 although the audible notificationwill be muted. In yet other embodiments, some alerts or alarms may notbe muted, such as, for example, high urgency alerts such low glucosealarms. In certain embodiments, some alarms may be muted forpredetermined periods of time regardless of user input. When an alarm ismuted, the user is presented with an option to accept (e.g., byactuation of a softkey button corresponding to the “Accept” softkeylabel 920) the mute setting and subsequently confirm the mute setting.If the user wishes to unmute the alarms, the user is presented with anunmute option and then may be prompted, via a display screen, to confirmthe unmute action.

The “Glucose Alarms” menu setting enables a user to specify when variousalarms of the analyte monitoring device 200 (FIG. 2A) are active. Theoptions presented to a user may specify the time of day that day alarmsbegin (e.g., 8:00 AM) and a time of day that the night alarms begin(e.g., 9:00 PM). In certain embodiments, the day alarm and the nightalarm cannot overlap. Additionally, the day and night alarms may havedifferent settings corresponding to how often the alarms are outputand/or under what conditions the alarms are output (e.g. low and highglucose thresholds). For example, the alarms setting may specify thatalarms are output during the day more frequently than alarms that areoutput at night. In certain embodiments, the time of the day alarm andthe time of the night alarm may be user adjustable and selectable. Inone aspect, day alarms may be active while night alarms are inactive.

In certain embodiments, when the day alarm time has been set, the menulinearly progresses to a “Glucose Alarm” threshold screen in which auser may select varying glucose threshold levels at which various alarmswill sound for low glucose levels, high glucose levels, projected lowglucose levels and projected high glucose levels. An exemplary “GlucoseAlarm” threshold display screen 1000 is shown in FIG. 10. In certainembodiments, the “Glucose Alarm” display screen 1000 includes a title1010 and a selection indicator 1020. The “Glucose Alarm” display screen1000 also includes a “Low Glucose” threshold level menu item 1030, a“High Glucose” threshold level menu item 1040, a “Projected Low” menuitem 1050, and a “Projected High” menu item 1060. Each menu item abovemay be selected using a jog wheel 230 (FIG. 2C) or other selectionmechanism. As shown in FIG. 10, a low glucose threshold level 1030 mayhave a preset low threshold (e.g., 80 mg/dL) and the high glucosethreshold level 1040 may have a preset high threshold (e.g., 250 mg/dL).In certain embodiments, the low glucose threshold level may be selectedby a user or healthcare provider from a predetermined range (e.g.,60-119 mg/dL) and the high glucose threshold level may be selected by auser or healthcare provider from a second predetermined range (e.g.,120-300 mg/dL). Each of the high and low threshold levels may be changedby the user or healthcare provider by highlighting the menu item usingthe selection indicator 1020 and inwardly pressing the jog wheel 230.The user may then scroll through the desired threshold level for theselected menu item.

In certain embodiments, a value for the “Projected Low” item 1050 andvalue for the “Projected High” item 1060 may be set in terms of time tfor each of the day alarms and the night alarms. The projected low valueand the projected high value represent how much notice a user wantsbefore an alert screen or alarm is output to notify a user of projectedglucose values that will exceed high or low glucose threshold limits.The time values may be set by selecting the particular menu item andactuating the jog wheel 230 as described above. In certain embodiments,the time values t may be in 10 minute increments ranging from 10 minutesup to 30 minutes. In other embodiments, varying time increments may beused. When desired settings are complete, the user may actuate a softkeybutton corresponding to the “Accept” softkey label 1070 and be returnedto a previous menu or to a home screen, such as, for example, homescreen 300 (FIG. 3A).

FIG. 11 illustrates an exemplary “Tones” menu display screen 1100 thatenables a user to select various tones for each of the low glucosethreshold level, the high glucose threshold level, the project low andthe project high settings. When the user has selected desired tones foreach of the low glucose threshold level, the high glucose thresholdlevel, the project low and the project high settings, the user mayaccept the settings by actuating a softkey button corresponding to thesoftkey label “Accept” 1160 or may navigate to a second “Tones” displayscreen by actuating a softkey button corresponding to the softkey label“Next” 1150.

In certain embodiments, the “Tones” menu display screen 1100 includes atitle portion 1110 indicating the name of the submenu as well as a listof available menu items 1140. In certain embodiments, the “Tones”display screen 1100 also includes a scroll indicator 1120 and a positionindicator 1125 that indicates a position of a selection indicator 1130.The “Tones” display screen 1100 displays different tones that may beused for each alarm of the analyte monitoring device 200 (FIG. 2 a). Incertain embodiments, additional tones or sounds may be downloaded fromthe internet and stored on the analyte monitoring device 200. The“Tones” menu display screen 1100 also gives users the option to turneach alarm on or off depending on the preference of the user, such asshown in FIG. 11 (e.g., the “Projected High” alarm is off).

In certain embodiments, data loss alarm tones and system alarm tones mayalso be selected by a user in the “Tones” menu display screen 1100. Thedata loss and system alarm tones may be controlled, muted and turned onor off much like the other tones described above. The data loss alarmindicates that glucose data is no longer available (e.g., the glucosedata has been deleted from the memory of the analyte monitoring device200) or glucose data has not been received from the sensor 101 for apredetermined amount of time (e.g., 10 minutes). In certain embodiments,if data loss continues for the predetermined amount of time, additionaltones may be output and/or display screens displayed that indicate thedata loss condition. In certain embodiments, data loss alarms must beactivated when glucose alarms are set. Thus, if a user sets an alarmtone for glucose levels exceeding a predetermined threshold, the usermust also select/activate an alarm tone for data loss. Regarding systemalarms, system alarms are output to notify a user of system events suchas a low battery or an upcoming need for calibration. As with data lossalarms, if a system alarm goes unheeded for a predetermined amount oftime, additional tones and display screens may be presented to the userto further notify the user of the condition of the various components ofthe system.

FIG. 12A shows a “Snooze Setup” display screen 1200 according toembodiments of the present disclosure. In certain embodiments, the“Snooze Setup” display screen 1200 includes a title portion 1210indicating the name of the display screen as well as a list of availablemenu items 1240. In certain embodiments, the “Snooze Setup” displayscreen 1200 also includes a scroll indicator 1220 and a positionindicator 1225 that indicates a position of a selection indicator 1230.The “Snooze Setup” display screen 1200 enables a user to selectdifferent snooze settings for the alarms of each of the low glucosethreshold level, the high glucose threshold level as well as projectedhigh and low glucose levels as described above. When the settings of theuser are selected, a user may actuate a softkey button corresponding tothe “Accept” softkey label 1250 to accept the snooze settings.

In certain embodiments, the snooze settings are in the range of 15minutes to 60 minutes in 5 minute increments for a low glucose thresholdlevel and the snooze settings for high glucose threshold level arebetween 15 minutes to 240 minutes in 5 minute increments. In certainembodiments, if an alarm is repeatedly “snoozed”, the command to snoozethe alarm is disregarded by the processor of the analyte monitoringdevice 200 and the alarm is continually outputted to notify the user ofthe condition or impending condition. In another embodiment, anotification (e.g., icon, message, etc.) of the alarm is output on thedisplay 210 as the home screen the next time the user interface of theanalyte monitoring device 200 is activated.

FIG. 12B is an exemplary “Charging Setup” display screen 1260 accordingto embodiments of the present disclosure. In certain embodiments, the“Charging Setup” display screen 1260 includes a title portion 1270indicating the name of the display screen as well as a selectionindicator 1280 that enables a user to select whether audio alarms areactivated when the analyte monitoring device 200 is charging. In certainembodiments, a user may select “no” if the user wants to disable audioalarms while the analyte monitoring device 200 is charging. In certainother embodiments, if the alarm settings of the analyte monitoringdevice 200 are set to vibration only or mute as described above withrespect to FIG. 8, selecting “yes” in the “Charging Setup” displayscreen 1260 causes the audio of the alarms to be output only when theanalyte monitoring device 200 is charging. When the analyte monitoringdevice 200 has been charged and is unplugged from an external powersupply, the audio for the alarms is disabled. Once the user has made thecharging setup selection, a user may actuate a softkey buttoncorresponding to the “Accept” softkey label 1290 to accept the chargingsetup setting.

FIG. 13 is an exemplary “Alarm Profile” display screen 1300 according toembodiments of the present disclosure. As with other display screensdescribed herein, the “Alarm Profile” display screen 1300 includes atitle portion 1310 indicating the name of the display screen as well asa list of available menu items 1340. In certain embodiments, the “AlarmProfile” display screen 1300 also includes a scroll indicator 1320 and aposition indicator 1325 that indicates a position of a selectionindicator 1330. The “Alarm Profile” display screen 1300 enables a userto select (e.g., by actuating a softkey button corresponding to the“Select” softkey label 1350), view and edit (e.g., by actuating asoftkey button corresponding to the “View/Edit” softkey label 1360)various alarm profiles that correspond to different activities of theuser. For example, a first alarm profile may correspond to exerciseactivities of the user while a second alarm profile may correspond toeating or sleeping activities of the user.

In certain embodiments, each alarm profile has parameter levelsassociated therewith, such as, for example, a low glucose level, aprojected low glucose level, a high glucose level and a projected highglucose level. The parameter levels for each alarm profile may be viewedand set similar to the glucose alarm threshold screen shown anddescribed with respect to FIG. 10.

Each profile also has a low glucose parameter 1410, a high glucoseparameter 1430, a projected low glucose parameter 1420 and a projectedhigh glucose parameter 1440 such as displayed in the “Day” displayscreen 1400 in FIG. 14. In certain embodiments, values for each of thelow glucose parameter 1410, the high glucose parameter 1430, theprojected low glucose parameter 1420 and the projected high glucoseparameter 1440 may be adjusted by a user. When the user has selected thedesired values for each parameter, the user may accept the changes byactuating a softkey button corresponding to the “Accept” softkey label1450. Further, the user may navigate to an additional display screen,such as, for example, display screen 1500 (FIG. 15) by actuating asoftkey button corresponding to the “Next” softkey label 1460.

Additionally, each profile also has parameters corresponding to whetheralarms for low glucose 1510, high glucose 1530, projected low glucose1520 and projected high glucose 1540 are turned on or off as shown indisplay screen 1500 of FIG. 15. When the user has selected the desiredvalues for each of these parameters, the user may accept the changes byactuating a softkey button corresponding to the “Accept” softkey label1550. Further, the user may navigate to an additional display screen,such as, for example, display screen 1600 (FIG. 16) by actuating asoftkey button corresponding to the “Next” softkey label 1560. Whencreating a profile, a user may also select alarm tones for data loss1610, in which tones or alarms are output when glucose data is no longeravailable or has not been received, and/or tones for systemnotifications 1620, such as low battery events and calibration events,and accept the settings by actuating a softkey button corresponding tothe “Accept” softkey label 1630 such as shown on display screen 1600 ofFIG. 16.

Each profile may also include specific alarm presentationcharacteristics such as alarm tone and/or volume setting. For example,if the user selects a “sleeping” profile, the parameters of the alertmay include a loud hypoglycemia alarm and a very high hyperglycemiathreshold. If the user selects an eating profile, the parameters of thealert may only include a high hyperglycemia threshold. The user maycustomize the setting of each profile or create a new profile to definea commonly used set of alarm parameters. Thus, the user does not need tochange each alarm setting based on various activities. In certainembodiments, a processor of the analyte monitoring device 200 may trackan active profile state which contains modifications to a definedprofile that are made on the fly by the user and implement those changesto similarly defined profiles.

Reports

When the “Reports” menu item is selected from the menu screen 600 (FIG.6) a “Reports” submenu is displayed according to embodiments. The“Reports” submenu enables a user to view glucose history by selecting a“Glucose History” submenu item, event history by selecting an “EventHistory” submenu item, a timeline graph by selecting a “Timeline Graph”submenu item, continuous glucose monitoring statistics by selecting a“CGM Statistics” submenu item, and blood glucose statistics by selectinga “BG Statistics” submenu item.

In certain embodiments, selection of “Glucose History” submenu itemenables a user to view past and continuous glucose information invarious time periods. These time periods may include 10 minute timeperiods, 60 minute time periods, or 120 minute time periods. When aparticular time period for the glucose history is selected (e.g., a 60minute time period), a user may view continuous glucose monitoringhistory for specific days in the time increment specified.

The “Glucose History” submenu also enables a user to view the bloodglucose history of the user. The blood glucose history display screenoutputs the time and date of each blood glucose reading as well asindicating, via text, colors, icons, or combinations thereof, as towhether the reading was high or low. A jog wheel, such as, for example,jog wheel 230 (FIG. 2C) allows a user to chronologically advance tonewer or older records in the user's history.

In certain embodiments, the “Glucose History” submenu also includes a“Glucose Alarms” display screen which allows a user to view recentalarms, including the type of alarm, that have been output based onglucose levels exceeding predetermined threshold levels such asdescribed above. Such alarm types may include alarms for low glucoselevels, alarms for high glucose levels as well as alarms for projectedhigh and low glucose levels. The jog wheel 230 may also be used tochronologically display various records stored in a memory of theanalyte monitoring device 200.

The “Event History” submenu item enables a user to review, enter, and/oredit various events the user has participated in during a specified timeperiod. Such events include: 1) the administration of insulin as well asthe type (e.g., short-acting, rapid-acting, long-acting, pre-mixintermediate, etc.) and amount of insulin injected (e.g., 0.00-99.50 U);2) food eaten, including the meal and the total number of carbohydrates(e.g., 0-350 g); 3) exercise, including the type of exercise (e.g.,aerobics, walking, jogging, running, swimming, biking, weights, other,etc.), the duration (e.g., 1-12 hours) and the intensity of the exercise(e.g., high, medium, low, none); 4) a state of health including editablefields describing the state of health (e.g., normal, cold, sore throat,infection, tired stress, fever, flu, allergy period, dizzy, feel low,feel high etc.); and 5) a custom field in which a user may viewcustomized events that affected or may have affected glucose levels.

In certain embodiments, when the “Timeline Graph” submenu item isselected by a user, a display screen, similar to the timeline graph 400of FIG. 4A, is output on the display 210 (FIG. 2A). The timeline graphdisplays glucose value data points versus a time of day for variousperiods of time. The timeline graph may also be configured to displayglucose values that fall within a user selectable target range. Forexample, a user may choose to have the timeline graph display onlyglucose values that fall within a range of 100 mg/dL-160 mg/dL within agiven period of time. Although a specific range has been discussed, itis contemplated that any range of values may be selected and displayed.As stated above with reference to FIG. 4A, the periods of time may beuser selectable to show a greater or fewer amounts of time. The jogwheel 230 may be used to chronologically navigate to earlier periods oftime or later periods of time represented on the timeline graph.

FIGS. 17A and 17B illustrate exemplary “CGM Statistics” (continuousglucose monitoring) display screens 1700 and 1750 according toembodiments. In general, each of the “CGM Statistics” display screens1700 and 1750 allow a user to view information about continuous glucosereadings received from a sensor, such as, for example sensor 101 (FIG.1). In certain embodiments, the “CGM Statistics” display screens 1700and 1750 also include a plurality of softkey labels 1790 (labeled “Home”and “Next”) to assist a user in navigating through various screens andsubmenus.

In certain embodiments, “CGM Statistics” display screen 1700 includes atitle portion 1710 to indicate the type of data the user is currentlyviewing. A user selectable time period display 1720 is also output onthe display screen 1700 to indicate the time period of the displayedstatistics. In certain embodiments, the time period is adjustable byselecting the time period display 1720 and actuating the jog wheel 230(FIG. 2C). CGM statistics may be viewed for 1, 3, 7, 14, 21, or 28 dayperiods.

In certain embodiments, “CGM Statistics” display screen 1700 alsoincludes a pie chart 1730 and a corresponding key 1740. The informationdisplayed on the pie chart 1730 and corresponding key 1740 includes apercentage of time the user's glucose level was above a target thresholdamount, a percentage of time the user's glucose level was within thetarget threshold amount, and a percentage of time the user's glucoselevel was below the target threshold amount. Although a pie chart isspecifically mentioned and shown, it is contemplated that other chartsand graphs, such as bar graphs may be used to display similar data.Additionally, the pie chart 1730 and the corresponding key 1740 may becolor coded to enable a user to easily identify which percentagescorrespond to which glucose levels. For example, a first line of text ofthe key 1740 and/or a first portion of a pie chart 1730 may be displayedin green to indicate the user was within the target range for 75% of thetime, a second line of text of the key 1740 and/or a second portion of apie chart 1730 may be displayed in yellow to indicate the user was belowthe target range for 15% of the time, and a third line of text of thekey 1740 and/or a third portion of the pie chart 1730 may be displayedin purple to indicate the user was above the target range 10% of thetime for a given time period.

FIG. 17B shows an additional “CGM Statistics” display screen 1750according to embodiments of the present disclosure. “CGM Statistics”display screen 1750 includes a title 1760 to indicate to a user the typeof data displayed. A user selectable time period display 1770 is alsodisplayed indicating the time period of the displayed statistics. Incertain embodiments, the time period is adjustable by selecting the timeperiod display 1770 and actuating the jog wheel 230 (FIG. 2C). CGMstatistics may be viewed for 1, 3, 7, 14, 21, or 28 day periods. “CGMStatistics” display screen 1750 also displays a list of statistics 1780such as an average continuous glucose level for the selected timeperiod, the standard deviation for the selected time period, a highestcontinuous glucose level for the selected time period, and a lowestcontinuous glucose level for the selected time period. In certainembodiments, additional statistics for the selected time period may bedisplayed, such as, for example, a low/day, high/day, projected low/dayand projected high/day.

Another embodiment of a “CGM Statistics” display screen 1701 is shown inFIG. 17C in which a user may scroll through statistical informationabout continuous glucose readings such as, for example, percentage oftime above a target threshold 1711, percentage of time within the targetthreshold 1721, a percentage of time below the target threshold 1731,and an average glucose value 1741 to name a few. When a user hasfinished viewing the “CGM Statistics” display screen 1701, the user mayreturn to a home screen, such as, for example information mode homescreen 300 (FIG. 3A) by actuating a softkey button corresponding to the“Home” softkey label 1751 or may return to a previously viewed displayscreen by actuating a softkey button corresponding to the “Done” softkeylabel 1761.

In certain embodiments, a “BG Statistics” display screen enables a userto scroll through historical information corresponding to blood glucosereadings. Such information may be output on the display 210 (FIG. 2A) asa pie chart, text, graphic or combination thereof in a similar fashionto the “CGM Statistics” display screen shown in FIG. 17A and describedabove. In certain embodiments, the information displayed on the “BGStatistics” display screen indicates a number of days or the number oftimes the user's blood glucose levels were above a target thresholdamount, within the target threshold amount, and below the targetthreshold amount.

In certain embodiments, other statistics may be available on the “BGStatistics” display screen such as, for example, an average bloodglucose level, the standard deviation, a highest blood glucose level,and a lowest blood glucose level. These statistics may be displayed in asimilar fashion to the “CGM Statistics” display screen shown in FIG. 17Band described above. This “BG Statistics” display screen may alsodisplay the total number of blood glucose readings in a given timeperiod, an average of the number of blood glucose readings per day inthe given time period, as well as above/day statistics and below/daystatistics. Each of the above mentioned statistics may be viewed forvarious time periods. For example, the given time periods may beselected from 1, 3, 7, 14, 21, or 28 day periods.

Add Event

When the “Add Event” menu item is selected, a submenu is output on thedisplay 210 that enables a user to enter in various events the user hasparticipated in during specific time periods. Such events include: 1)the administration of insulin as well as the type (e.g., short-acting,rapid-acting, long-acting, pre-mix intermediate, etc.) and amount ofinsulin injected (e.g., 0.00-99.50 U); 2) food eaten, including the mealand the total number of carbohydrates (e.g., 0-350 g); 3) exercise,including the type of exercise (e.g., aerobics, walking, jogging,running, swimming, biking, weights, other, etc.), the duration (e.g.,1-12 hours) and the intensity of the exercise (e.g., high, medium, low,none); 4) a state of health including editable fields describing thestate of health (e.g., normal, cold, sore throat, infection, tiredstress, fever, flu, allergy period, dizzy, feel low, feel high etc.);and 5) a custom field in which a user may view customized events thataffected or may have affected glucose levels. Once an event has beenentered, an event icon may be displayed at a point on the timeline graph400 (FIG. 4A) at the current continuous monitored glucose levelcorresponding to the current time of the analyte monitoring device 200.In one aspect, if the user failed record an event at the time it tookplace, the user may be able to manually select a time period in whichthe event took place and it is recorded on a graph at the time periodselected by the user.

Status

FIG. 18 illustrates an exemplary “Status” display screen 1800 accordingto embodiments of the present disclosure. The “Status” display screen1800 includes iconic representations of the status of various componentsof the analyte monitoring device 200. As with other display and menuscreens, “Status” display screen 1800 includes a title portion 1810 anda plurality of softkey labels 1820 (labeled “Home” and “Next”) to assista user in navigating to and from the “Status” display screen 1800.Although two softkey labels 1820 are shown, it is contemplated that anynumber of softkey labels may be displayed on the “Status” display screen1800.

In certain embodiments, the “Status” display screen 1800 includesvarious icons and corresponding text about the status of variouscomponents of the analyte monitoring device 200 (FIG. 2A) and/or theanalyte monitoring system 100 (FIG. 1). The icons and corresponding textmay include a battery power icon 1830 that shows available battery powerin the analyte monitoring device 200, audio and vibrating settings icon1840, a wireless connection status icon 1850 that indicates theconnection status between the analyte monitoring device 200 and thetransmitter, such as, for example transmitter unit 102 (FIG. 1), atransmitter battery charge icon 1860 that indicates the battery powerremaining in the transmitter and a calibration status icon 1870. Eachicon may have corresponding text to indicate what the icon represents.

The “Status” display screen 1800 may also include additional displayscreens that display the status of the various components of the analytemonitoring system 100 and/or the analyte monitoring device 200. Forexample, the user may be provided sensor information, such as, the dateand time of the next calibration. This display screen may also indicatea calibration grace period available to the user. The user may also benotified of the life remaining on the current sensor as well as the dateand time the current sensor is set to expire. Although this informationis provided in the status screen, it is contemplated that thisinformation may be presented on a home screen, such as information modehome screen 300 (FIG. 3A).

The “Status” display screen 1800 may also display the amount of timethat has elapsed since the analyte monitoring device 200 receivedupdated data from the sensor. Additionally, the “Status” display screen1800 may display information regarding the status of the sensor.Examples include, a last reset, sensor errors, calibration failedindicator and the reasons for each (e.g., temperature too high,temperature too low etc.). In certain embodiments, the serial number andtype of the transmitter may be displayed on the “Status” display screen1800 as well as a serial number and software versions of the analytemonitoring device 200. The serial number of the analyte monitoringdevice 200 and/or the transmitter may be displayed using numbers,letters, symbols, or a combination thereof.

Settings

The “Settings” menu type may include various display screens to assist auser in changing various settings of the analyte monitoring device 200.Examples include a “Time and Date” display screen, a “Display” settingsdisplay screen, a “Glucose Targets” display screen, a “Self Test”display screen and a “Training” display screen. The “Time and Date”display screen enables a user to adjust the time and date displayed onthe user interface. The “Display” settings display screen provides auser with a number of different options including a language setting, atimeout setting and a decimal format setting. The language settingenables a user to select at least 11 different languages (e.g., English,Spanish, German, Dutch, Portuguese etc.) of the text displayed on thedisplay 210 the analyte monitoring device 200. The timeout settingenables a user to select a period of inactivity, from 15 seconds to 120seconds, until the display 210 shuts off and/or the analyte monitoringdevice 200 enters a sleep mode. Upon exiting the sleep mode, such as,for example, by a user actuating a softkey button or touching a touchsensitive display, a home screen is output on the display 210 of theanalyte monitoring device 200. In one aspect, when exiting the sleepmode, the display screen that was output on the display 210 prior toentering the sleep mode may be output on the display 210. In certainembodiments, the decimal setting enables a user to select a decimalformat of either X.X or X,X.

The “Glucose Target” display screen enables a user to adjust the upperand lower target glucose amounts displayed on graphs such as, forexample lower glucose target indicator 312 (FIG. 3A) and an upperglucose target indicator 314 (FIG. 3A), and are used to calculate auser's statistics reports. In certain embodiments, the “Glucose Target”display screen may be locked or password protected to preventunauthorized or unintentional alteration of the glucose target range.

In certain embodiments, a “Self Test” display screen enables a user toselect and run a self test mode in which the analyte monitoring device200 automatically self tests whether various components of the analytemonitoring device 200 are working properly. Such components include thedisplay, the speaker, the memory, the vibratory indicator, and the stripport light. After each successive test, the results may be audiblyand/or visually output to a user. Although specific self tests have beenmentioned, it is contemplated that additional self tests related toother components of the analyte monitoring device 200 may be performed.

In certain embodiments, the “Settings” menu type may also include a“Training” display screen in which a user may select to enter a trainingmode. The training mode is provided to assist a user in becomingfamiliar with the analyte monitoring device 200 and the various alertscreens or display screens that may be output on the display 210 analytemonitoring device 200. As such, preloaded data may be used to triggeralarms and/or populate graphs thus giving a user firsthand experience inhow the analyte monitoring device 200 operates and what conditionstrigger the various alarms and alerts. Additionally, battery life of theanalyte monitoring device 200 may be extended for a predetermined amountof time as some capabilities (e.g., wireless capabilities) and/orcomponents of the analyte monitoring device 200 may be deactivatedduring training mode.

In certain embodiments, access to the training mode may be protected bya password to prevent unauthorized or unintentional access by a user. Inanother embodiment, the training mode may be freely accessed by the userbut various features and options of the training mode, such as maskingand unmasking data, may be password protected. During training mode auser may have an option in which the display 210 of the analytemonitoring device 200 will not time out for a user selectable period oftime. In training mode a user may also erase glucose related data andreset user settings or user logs of the analyte monitoring device 200.

In training mode, a user may be able to select various training options.For example, a first option may correspond to setting event data iconson a graph such as event data icons 318 (FIG. 3C). The training mode maycontain a simulation of various glucose levels and how each activity mayaffect subsequent glucose readings and data display. A second type oftraining mode may correspond to setting up various profiles based onuser activities such as described above. Regardless of which trainingmode is selected, when the training is complete, the user may erase alltraining data from the analyte monitoring device 200.

In certain embodiments, training mode may also randomly select alarmsand/or display screens from a set of predetermined alarms and displayscreens that a user is most likely to encounter when using the analytemonitoring device 200, such as, for example a low glucose alarm displayscreen. When the low glucose alarm display screen is output on thedisplay 210, a message screen may be output on the display 210instructing the user on how to proceed to deactivate the alarm and howto enter event history on a graph if desired.

In another embodiment, the training mode may receive real time data froma transmitter and perform functions as if in “normal” mode. At variouspoints in the training mode, various display screens may be output onthe display 210 instructing a user on what functions or display screensmay be helpful to the user based on the data received. For example, if aglucose data value is received that is above or below a targetthreshold, the user may be prompted, via a display screen, to navigateto an alarms screen or a glucose level threshold display screen. Thedisplay screen may also contain written text or visual indicatorsinstructing the user how to navigate to the suggested display screen.

When in training mode, a user may also choose to mask and/or unmask datacorresponding to continuous glucose readings and blood glucose readings.In certain embodiments, when data from either continuous glucosereadings or blood glucose readings is masked, corresponding alarms foreach of the readings are deactivated. In certain other embodiments, whendata is masked, certain menu items and/or display screens associatedwith the masked data may be deactivated.

Manual Calibration

In certain embodiments, the menu screen 600 (FIG. 6) may also include a“Manual Calibration” menu item in which a user is prompted, via adisplay screen, to determine if they want to manually calibrate thesensor of the analyte monitoring system 100 (FIG. 1). If a user wishesto proceed with the manual calibration of the sensor, instructions areoutput on the display 210 of the analyte monitoring device 200 asdescribed above.

FIG. 19 illustrates an exemplary alert screen 1900 according toembodiments of the present disclosure. As shown in FIG. 19, an alertscreen 1900 may be output on the entire surface area of the display 210(FIG. 2A) of the analyte monitoring device 200. In certain embodiments,the alert screen 1900 includes a title portion 1910 that indicates thatnature of the alert (e.g., “Low Glucose”). In one aspect, the alertscreen 1900 may be displayed in one or more panels of a home screen,such as, for example, panel 303 of information mode home screen 300(FIG. 3A). If a first alert condition is detected and a second alertcondition is detected prior to the first alert condition being resolved,a higher priority alert may be displayed in place of the lower priorityalert. In certain embodiments, both alerts may be displayed in twoseparate panels of the home screen. For example, the first alert may bedisplayed in the first panel 303 of the information mode home screen300, while the second alert is simultaneously displayed in the secondpanel 320 of the information mode home screen 300.

The alert screen 1900 also includes information 1920 regarding thecondition that triggered the alert. For example, and as shown in FIG.19, the displayed information 1920 indicates that the user currently hasa glucose level of 74 mg/dL which is below a predetermined thresholdlevel of 75 mg/dL. Further, the alert screen 1900 shows that the user'sglucose level is rapidly decreasing as indicated by the downward arrow1940. Additional exemplary alert screens are shown in FIGS. 20 and 21.

In certain embodiments, actuation of the secondary button 240 (FIG. 2C)or another softkey button such as, for example, input button 220, whenan alert screen is displayed, causes the display 210 to output a displayscreen that corresponds to the detected alert condition. For example, ifthe alert condition corresponds to a glucose level that is below apredetermined threshold, actuation of the secondary button 240, oranother softkey button, may cause the display 210 to output a graph,such as for example, graph 400 (FIG. 4A), that shows glucose data andcorresponding events (e.g., exercise, meals, bolus doses etc.) that mayhave contributed to the alert condition. Additionally, actuation of thesecondary button 240 or other softkey button when an alert screen isdisplayed may cause the display 210 to output an alarm setting displayscreen in which the user may select to silence or mute the alarmassociated with the alert condition for a predetermined period of time.In certain embodiments, the display screen that is output upon actuationof the secondary button 240 when an alert screen is displayed may varybased on the type of the alert detected. For example, if the alertscreen corresponds to a low urgency alert, actuation of the secondarybutton 240 causes a first display screen to be output on the display210. Further, if the alert screen corresponds to high urgency alert,actuation of the secondary button 240 causes a second display screen tobe output on the display 210.

Although specific alert screens are specifically described above, it iscontemplated that various other alerts may be output on the display 210of the analyte monitoring device 200. Examples of alert screens that maybe output on the display 210, along with the meanings of the alertscreens are as follows: “CGM is not available. Check your BG in 3 hoursto calibrate.”—which may indicate that the sensor signal is settling andglucose results may not be accurate, the system has stopped reportingglucose results and will ask for another calibration in 3 hours, andglucose alarms are not active; “Calibration BG out of range (60-400mg/dL). Check your BG later to calibrate.”—which may indicate that theuser's blood glucose results is too low or too high; “Check your BG in15 minutes to calibrate.”—which may indicate that the calibration testwas very different from the previous calibration; “Check your BG in 1hour to calibrate.”—which may indicate that calibration failed for oneof several possible causes which includes 1) information from thetransmitter was incomplete; 2) there was no communication between thetransmitter and the analyte monitoring device; 3) the sensor may not beworking properly; and 4) the user's glucose levels have been changingrapidly; “Receiver temperature out of range. Check your BG in 1 hour tocalibrate.”—indicating calibration failed because the analyte monitoringdevice was too warm or too cold; “CGM is not available. Check your BG tocalibrate.”—indicating that the calibration has expired and glucosealarms are not active; “Check your BG to confirm your lastcalibration.”—indicating the sensor signal may still be settling and thesystem requires another calibration to confirm the sensor signal;“Charge receiver soon.”—indicating that there is less than 25% of chargeremaining; “Charge receiver immediately.”—indicating that less than 15%of charge is remaining; “Receiver will lose all power soon. ChargeReceiver immediately.”—indicating that no charge is remaining and theanalyte monitoring device could shut down at any time; “Receivertemperature is low. Warm up Receiver to maintain power.”—indicating theanalyte monitoring device temperature is too cold; “CGM not available.Connect to Sensor.”—indicating that the analyte monitoring device hasnot been receiving signals sent by the transmitter, and the analytemonitoring device is either too far from the transmitter or there arematerials or signals causing interference and glucose alarms are notactive; “Transmitter Battery is low. Replace the Transmitter with thenext Sensor.”—indicating the transmitter battery has less than 10%charge; “Need to replace Transmitter in 2 months. Contact customerservice.”—indicating the transmitter battery has less than 20% charge;“CGM is not available. Ensure the Sensor is firmly attached.”—indicatingthat there is an unstable sensor signal, glucose cannot be calculated,and glucose alarms are inactive; “CGM not available. Replace the Sensorto continue CGM.”—indicating that glucose has not been calculated forthe past 60 minutes and glucose alarms are not active; “CGM is notavailable. Sensor life is complete. Replace the Sensor to continueCGM.”—indicating that alarms are not operating because the 5-day life ofthe sensor has ended and glucose alarms are not active; “Did you Removethe Sensor? Select ‘Yes’ to end CGM.”—indicating that the system hasdetected that the sensor was just removed or that the sensor may bepulling out of the user's skin; “Sensor life nearly complete. Replacethe Sensor by (date and time)”—indicating that the sensor will reach theend of its life within 2 hours; “The skin near the sensor is too[cold/warm] for calibration. [Warm up/Cool down] your skin.”—indicatingthat the user's skin temperature may be out of range for calibration;“CGM is not available. The skin temperature near the Sensor is too coldor warm; “Correct to continue CGM.”—indicating the skin is too cold ortoo warm to display continuous glucose readings and that glucose alarmsare not active; “Check your BG to Calibrate.”—indicating a blood glucosereading is needed for calibration in which case the analyte monitoringdevice prompts the user to perform this test approximately 1, 2, 10, 24and 72 hours after a new sensor is inserted; and “Transmitter hasdetached from Sensor. CGM is not available. Replace the Sensor tocontinue CGM.”—indicating the transmitter is not firmly attached to thesensor and glucose alarms are not active.

In certain embodiments, additional error screens showing “BG check notavailable”, “Er 1”, “Er 2”, “Er 3”, and “Er 4” may be output on thedisplay 210 when a user is checking blood glucose levels. Such errorscreens may indicate that the analyte monitoring device 200 is chargingwhile a user is trying to perform a blood glucose test, the blood sampleon the test strip is too small, the blood glucose of the sampled bloodis very low (e.g., less than 20 mg/dL) or very high (greater than 500mg/dL), there is a problem with the test strip or analyte monitoringdevice 200, control solution labeled HIGH is applied when thetemperature is too cold, or the blood glucose procedure was notperformed correctly, such as, for example, putting blood on the teststrip before inserting the test strip into the test port.

Although specific alert screens have been described above, it iscontemplated that additional alert screens may be output on the display210, with each of the alert screens falling into variousclassifications. These alerts include low urgency alerts, intermediateurgency alerts, medium urgency alerts, and high urgency alerts. Eachclassification of alert may have varying tones, alarms, display colorsand alert display screens associated therewith. For example, low urgencyalert display screens may be output in a first color, intermediateurgency alert display screens may be output in a second color, mediumurgency alerts may be output in a third color and high urgency alertsmay be output in a fourth color. Additionally, each of the alerts mayinclude fixed text or context-dependent text. For example, a projectedalarm may include the current glucose value and trend, the alarmthreshold, or the time horizon of the alarm projection. In one aspect,alert messages may include icons, graphs or other indicators dependingon whether the alarm relates to device malfunctions, analyte levels, orthe need to calibrate the sensor.

In certain embodiments, a low urgency alert is provided when a conditionoccurs which is of low priority. Such low urgency alerts may correspondto malfunctions of the analyte monitoring device 200. For example, a lowurgency alert may be provided when a history log is corrupted, a loss ofsettings of the analyte monitoring device 200, a broken strip portlight, a broken speaker, a broken vibratory indicator, a need toestablish a link, a transmitter battery warning or a cleared history.

In certain embodiments, a low urgency alert is output on the display 210as a yellow message screen. To bypass the screen, the user may berequired to actuate a softkey button corresponding to a softkey labeldisplayed on the message screen. In addition to displaying the message,a low urgency alert tone and/or vibration may be output from the analytemonitoring device 200 depending on selected user settings. Low urgencyalerts may be silenced after the low urgency alert is displayed or alllow urgency alerts may be muted by a user.

Intermediate urgency alerts are output when a condition occurs that ismore important than low urgency alerts. In certain embodiments,intermediate urgency alerts correspond to various calibration conditionssuch as those described above. For example, intermediate alerts may beoutput upon occurrence of a request for calibration, a failedcalibration because a fingerstick reading is too high, too low orinvalid, unsuitable pre-calibration conditions because skin temperatureis too high or too low, or a failed calibration because skin temperatureis too high or too low. In another embodiment, immediate urgency alertsmay notify a user to remove a test strip from a test strip port or tore-sync the transmitter and analyte monitoring device 200.

Intermediate urgency alerts may be output on the display 210 of theanalyte monitoring device 200 as a yellow message screen. Each alert mayhave accompanying alarms and vibration settings, each of which are userselectable. Intermediate urgency alerts may also be output repeatedlyfor a predetermined amount of time until addressed by the user or untilthe user puts the alert “on hold.” In certain embodiments, anintermediate alert may be put “on hold” or “snoozed” for a predeterminedamount of time (e.g., 5 minutes). If the intermediate alert is notaddressed after the “on hold” time has elapsed, the alert, including themessage screen and/or the tactile/audible alarm, is output a secondtime. Intermediate alerts may be silenced when the alert message isacknowledged by the user or the condition that triggered the alertceases to exist. As discussed above, the alarm tones and snooze time ofintermediate alerts may be user selectable.

In certain embodiments, a medium urgency alert is provided when acondition occurs that is a higher priority than the intermediate urgencyalert. In certain embodiments, a medium urgency alert corresponds to theoccurrence of a high glucose condition, a projected high glucosecondition or a projected low glucose condition. In a medium urgencyalert, an alarm and a yellow alert screen are output on the display 210on the analyte monitoring device 200. As with other alarms, the alarmtone, duration and volume for the medium urgency alert may be userselectable. Based on a user's settings, the alarm may be output in 6second increments for one minute until the alert is acknowledged.However, once the user acknowledges the alert, the alert may be put “onhold” or “snoozed” for a user selectable time period (e.g., 5 minutes)by actuating a softkey button on the analyte monitoring device 200.

In certain embodiments, medium urgency alerts may be “acknowledged” andput on hold for various periods or amounts of time based on userselection. An acknowledgement may occur when user actuates a softkeybutton associated with a particular softkey label on the display 210 ofthe analyte monitoring device 200. If the user selected“acknowledgement” time period passes and the condition that triggeredthe medium urgency alert still exists, a high urgency alert, including ahigh urgency alert display screen and/or audible/tactile notificationmay be output by the analyte monitoring device 200. Medium urgencyalerts are deactivated when the condition that triggered the alertceases to exist. As with other alerts described above, the alarm tonesand snooze feature of the medium urgency alert are customizable by auser.

In certain embodiments, a high urgency alert is provided when lowglucose condition are detected, such as, for example, the low glucosecondition shown above with respect to FIG. 19. The display screen of ahigh urgency alert may be output on the display 210 of the analytemonitoring device 200 as a red display screen. If the user interface ofthe analyte monitoring device 200 is not active (e.g., in a sleep mode),a high urgency alarm is output once every six seconds for apredetermined amount of time. If the user interface of the analytemonitoring device 200 is active, the high urgency alert is output on thedisplay 210. As with other alerts, actuation of a softkey button may putthe high urgency alert on hold for a predetermined amount of time. Highurgency alerts may be put on hold for user selectable periods of time ifthe user acknowledges the alert and actuates a softkey buttoncorresponding to an acknowledgement softkey label. If the same highurgency alert condition still exists after the acknowledgement periodexpires, the high urgency alert is output a second time. In certainembodiments, high urgency alerts are silenced when the condition thattriggered the high urgency alert ceases to exist. In one aspect, highurgency alerts are not mutable.

FIG. 20-21 show additional exemplary alert screens according toembodiments of the present disclosure. Referring to FIG. 20, alertscreen 2000 includes a title portion 2010 indicating the nature of thealert screen (e.g., sensor out of range) and a message portion 2020 thatnotifies the user of the cause of the alert. Although text isspecifically shown in FIG. 20, it is contemplated that the text may bereplaced by an icon, a series of icons, video clip, sound byte etc.

In certain embodiments, when the alert screen 2000 has been output onthe display 210 (FIG. 2A) of the analyte monitoring device 200, the usermay attempt to connect the analyte monitoring device 200 to a sensor,such as, for example, sensor 101 (FIG. 1) by actuating a softkey buttoncorresponding to the “Connect” softkey label 2030. If the user does notwant to attempt to connect the analyte monitoring device 200 to asensor, the user may acknowledge the alert screen by actuating a softkeybutton corresponding to the “OK” softkey label 2040. Once the alertscreen 2000, has been acknowledged, the user is returned to a homescreen, such as, for example, home screen 300 (FIG. 3A).

Referring to FIG. 21, alert screen 2100 includes a title portion 2110indicating the nature of the alert screen (e.g., confirmation of a useraction) and a message portion 2120 that notifies the user of the causeof the alert. Although text is specifically shown in FIG. 21, it iscontemplated that the text may be replaced by an icon, a series oficons, video clip, sound byte etc.

In certain embodiments, when the alert screen 2100 has been output onthe display 210 (FIG. 2A) of the analyte monitoring device 200, the usermay attempt to establish a connection between the analyte monitoringdevice 200 and a transmitter such as, for example, transmitter unit 102(FIG. 1). The user may attempt to establish a connection between theanalyte monitoring device 200 and the transmitter by actuating a softkeybutton corresponding to the “Yes” softkey label 2140. If the user doesnot want to attempt to establish a connection between the analytemonitoring device 200 and the transmitter, the user may acknowledge thealert screen by actuating a softkey button corresponding to the “No”softkey label 2130. Once the alert screen 2100, has been acknowledged,the user is returned to a home screen, such as, for example, home screen300 (FIG. 3A).

FIG. 22 illustrates a method 2200 for displaying sensor data accordingto embodiments of the present disclosure. The routine for displayingsensor data begins when sensor data is communicated by a transmitter(2210), such as transmitter unit 102 (FIG. 1), and received by areceiving unit, such as receiving unit 104 (FIG. 1) or analytemonitoring device 200 (FIG. 2A). In certain embodiments, the sensor datacorresponds to an analyte level of a user, such as, for example, acurrent glucose level. In certain embodiments, the data is transmittedand received “on-demand” by placing the analyte monitoring device 200 inclose proximity with the transmitter unit 102 and initiating datatransfer, either over a wired connection, or wirelessly by variousmeans, including, for example, various RF-carried encodings andprotocols and IR links.

When the sensor data is received, a processor of the analyte monitoringdevice 200 outputs the data on a display screen of the analytemonitoring device 200 (2220). In certain embodiments, the receivedsensor data may be displayed on an information mode home screen such asdescribed above with reference to FIG. 3A. In such embodiments, thesensor data is plotted as a point on a graph that is output on a firstsection of the information mode home screen. The received sensor datamay also be simultaneously displayed in a second section of theinformation mode home screen as a numerical value of a current analytelevel. In one aspect, the sensor data may be stored in a memory of thetransmitter unit 102 or in a memory of the analyte monitoring device 200after it has been received and not displayed until additional sensordata is received.

As additional sensor data is obtained by the sensor (2230), theadditional sensor data may be transmitted by the transmitter unit 102and received by the analyte monitoring device 200 on-demand or atregular time intervals. When the additional sensor data is received, aprocessor outputs a numerical representation of the additional sensordata on the display in the second section of the information mode homescreen as the current analyte level. Additionally, when the additionalsensor data is received, the additional sensor data is plotted on thegraph corresponding to an analyte level on a y-axis at a time t on thex-axis that the data was received.

As additional sensor data is received by the analyte monitoring device200, the processor compares the previously received sensor data to theadditional sensor data (2240) to determine a rate of change and thetrend data between the two readings. In certain embodiments, this datamay be used to calculate and display the rate of change of the analytelevels of the user. Once the rate of change and/or trend data isdetermined, the rate of change is displayed on the graph portion of theinformation mode home screen (2250) with the current analyte level andtrend information being simultaneously displayed on a second portion ofthe home screen such as, for example, home screen 300 (FIG. 3A).

FIG. 23 illustrates a method 2300 for outputting an alert based on adetected alert condition according to embodiments of the presentdisclosure. The routine for outputting an alert based on a detectedalert condition begins when an alert condition is detected (2310) by aprocessor of the analyte monitoring device 200 (FIG. 2). In certainembodiments, the detected alert condition may correspond to low urgencyalerts, intermediate urgency alerts, medium urgency alerts, and highurgency alerts as discussed above. In certain embodiments, each of thealert levels may be arranged based on the urgency level and/or priority.Thus, if a low urgency alert is detected simultaneously with orsubstantially simultaneously with an intermediate urgency alert, theintermediate urgency alert is output by the analyte monitoring device200.

When an alert condition is detected, an alert screen, corresponding tothe detected alert condition, is output on the display of the analytemonitoring device 200 (2320). In certain embodiments, the alert screenmay correspond to the alert screen 1900 described above with respect toFIG. 19. Accordingly, each alert screen may be output on the entiresurface area of a display 210 of the analyte monitoring device 200. Thealert screen may include a title portion that indicates that nature ofthe alert and also includes information regarding what triggered thealert (e.g. high glucose level, sensor calibration etc.). In addition todisplaying alert screens, alarms and/or vibrations may be output tofurther inform the user of a detected alarm condition.

When an alert condition is detected, a processor of the analytemonitoring device 200 determines whether the detected condition has beenremedied (2330). In certain embodiments, the processor of the analytemonitoring device 200 issues a command to determine what triggered thealert condition and, based on received data corresponding to the alertcondition, whether the condition is ongoing. For example, if the alertcondition corresponds to a low battery alert of a battery of the analytemonitoring device 200, the processor may determine that the condition nolonger exists because the analyte monitoring device 200 is beingcharged. If it is determined that the condition has been remedied, theprocessor issues a command to terminate the alert (2340).

In certain embodiments, depending on the type of alert, variousconditions may need to be met prior to the alert being terminated. Forexample, if the alert is a high urgency alert, such as a low glucoselevel, a detected current glucose level may need to be at or above aminimum glucose threshold level for a predetermined amount of time. If,for example, the alert is a medium urgency alert, such as a projectedhigh glucose condition or a projected low glucose condition, the usermay need to take actions, such as, for example, administering a bolusinsulin dose to change the trend data associated with the alert.

In certain embodiments, if an alert screen has been displayed for adetected alert condition but no action has been taken within apredetermined amount of time (e.g. 1 hour), the processor may issue acommand to output subsequent notifications such as a follow-up alarm orvibration. In one aspect, subsequent notifications may be output onlyfor certain types of alert conditions, such as, for example high urgencyalerts. In another embodiment, subsequent notifications (e.g., tactile,audible, and/or visual) may be output for all types of alert conditions(e.g., low urgency alerts, medium urgency alerts etc.). As stated above,a user may have an option of muting alarms for some of the differenttypes of alerts described above (e.g., low urgency alert). In caseswhere the alarm has been muted, but no action has been taken regardingthe alert notification for a predetermined period of time, the processormay issue a command to override the mute setting and the alarm and/oralert notification is output.

As discussed above, each of the low urgency alerts, intermediate urgencyalerts, medium urgency alerts, and high urgency alerts may allow a userto put the alert on hold for a predetermined amount of time. When thepredetermined amount of time expires, the processor issues a command todetermine if the detected alert condition still exists. If it isdetermined that the condition still exists, the above process isrepeated until the detected alert condition is remedied.

In cases where the alert is a medium urgency alert, the “on hold” timepasses and the condition still exists, the medium urgency alert may beupgraded to a high urgency alert. Thus, the alert notification is outputwith a corresponding high urgency display screen and alarm tone.Although upgrading a medium urgency alert has been specificallydiscussed, it is contemplated that various other alert conditions may beupgraded from one level to another, such as, for example, a low urgencyalert being upgraded to an intermediate urgency alert.

FIG. 24A illustrates a flow chart 2400 for outputting display screensbased on a detected alert condition according to embodiments of thepresent disclosure. As shown in FIG. 24A, a processor of an analytemonitoring device, such as analyte monitoring device 200 (FIG. 2A) firstdetects a medical alert condition (2410). The detected medical alertcondition may correspond to a high urgency alert such as describedabove. The processor of the analyte monitoring device 200 may activatean alert notification, such as, for example, output an alarm tone and analert display screen, and simultaneously determine a softkey buttonlabel for a softkey button that will output a display screencorresponding to alert condition upon user actuation of the softkeybutton (2411 and 2412). When the user actives the analyte monitoringdevice 200, the alert screen associated with the alert condition isoutput on the display 210 of the analyte monitoring device 200 (2413).When the user actuates the softkey button associated with the softkeybutton label (2414) a second screen is output on the display 210 of theanalyte monitoring device 200 (2415). In certain embodiments, the secondscreen is a home screen such as, for example home screen 300 (FIG. 3).In an embodiment, the second screen corresponds to the detected alertcondition. For example, if the detected alert condition is a lowbattery, actuation of the softkey button with the corresponding softkeybutton label may take the user directly to a status display screen, suchas was described above with reference to FIG. 18.

In other examples, if the analyte monitoring device 200 detects a highglucose level and outputs an alarm, such as, for example, an alarm asshown in shown in FIG. 24B, the message may include a “Bolus” softkeylabel 2420 and an “Accept” softkey label 2422. If the user selects the asoftkey button associated with the “Accept” softkey label 2422, thedisplay 210 of the analyte monitoring device 200 returns to a homescreen, such as home screen 300 (FIG. 3A). However, if the user selectsa softkey button associated with the “Bolus” softkey label 2420, a boluscalculator screen may be output on the display 210 of the analytemonitoring device 200 (as depicted in FIG. 24C). The bolus calculatorscreen may display insulin information such as, for example, insulin onboard information, the correction bolus that was or is going to beapplied by an insulin pump and the total insulin bolus amount. Incertain embodiments, the bolus calculator screen may include an entryfield to allow a user to manually input bolus amounts. Additionally, thebolus calculator screen may include a softkey label 2424 (labeled as“Next”) which directs the user to another display screen comprisingadditional information corresponding to a bolus calculator. For example,actuation of a softkey button corresponding to the “Next” softkey label2424 could cause a help display screen corresponding to the boluscalculator to be output on the display 210.

In certain embodiments, the shortcut mechanism can also be used to takethe user to a display screen in which the user can modify the settingsof the alarm that is being output. For example, when an alarm is output,the user may want to mute further alarms, activate a snooze mode, turndown the volume, or place the analyte monitoring device 200 in vibrateonly mode. In certain embodiments, a plurality of shortcut mechanismsmay be programmed into the device based on, for example, a length of abutton press, a combination of buttons pressed etc.

As described above, some alert conditions are characterized by ananalyte level exceeding a threshold. In this manner, the detected alertcondition relates to a physiological condition of a user such ashypoglycemia, hyperglycemia, impending hypoglycemia, or impendinghyperglycemia. In certain embodiments, outputting an alarm meansproducing one or more notification signals associated with the alertcondition such as a visual message, an auditory message, a vibration, orother sensory-stimulating signals such as heat, cool, electrical shocketc. Notifications such as these can alert or warn a user of theoccurrence of a condition that either relates to the health of the useror to the functionality of the analyte monitoring device 200.

As discussed above, an alarm may be output when the signal from thesensor indicates the glucose level has exceeded or is about to exceed athreshold value. Some non-limiting examples of threshold values forblood glucose levels are about 60 mg/dL, 70 mg/dL, or 80 mg/dL forhypoglycemia, about 70 mg/dL, 80 mg/dL or 90 mg/dL for impendinghypoglycemia, about 130 mg/dL, 150 mg/dL, 175 mg/dL, 200 mg/dL, 225mg/dL, 250 mg/dL, or 275 mg/dL for impending hyperglycemia and about 150mg/dL, 175 mg/dL, 200 mg/dL, 225 mg/dL, 250 mg/dL, 275 mg/dL or 300mg/dL for hyperglycemia. Further, each of the conditions mentioned abovecan have different notification signals, such as different audible tonesor alarms, different alert screen colors, different screen brightness,different icons and the like. It is also contemplated that an alertcondition may be detected if sensor readings indicate a value is beyonda measurement range of the sensor.

In yet another embodiment, an alert condition may be detected when therate of change or acceleration of the rate of change in an analyte levelexceeds a threshold rate of change or acceleration. For example, theanalyte monitoring device 200 may be configured to output a dynamicglucose level alarm if the detected rate of change in glucoseconcentration exceeds a threshold rate of change for a predeterminedamount of time (e.g., the rate of change of glucose level detected overa specified period of time was in excess of 3-4 mg/dL/min). A rate ofchange such as described may indicate that a hyperglycemic orhypoglycemic condition is likely to occur. Although specific rates ofchange have been mentioned, it is contemplated that the rate of changethreshold and the time period associated with the rate of change may beselected and adjusted by the user or a health care provider.

In certain embodiments, the alarm tone for the dynamic glucose levelalarm may be a unique alarm such that the user is more readily warned ofthe possible pending condition. As such, in one embodiment, thisparticular alarm may be preset and the user may not have the option toselect a new alarm tone. In another embodiment, the alarm tone may beuser selectable but only from a tone library that is separate and uniqueand a tone library that may be used by other alarms of the analytemonitoring device 200. Additionally, the display of the analytemonitoring device 200 may display a rate of change arrow thatsuccessively flashes on and off to give the user a visual indicationthat the user's glucose levels have been rising or falling at a rategreater than the threshold rate of change for over the predeterminedtime period.

The dynamic glucose level alarm is provided to assist a user who mayhave underestimated the carbohydrates of a meal. Additionally, thedynamic glucose level alarm can also serve as an emergency warning whenerrors are made in restaurants or in the home and users are mistakenlygiven high-carbohydrate food or drinks when they were expecting and hadprepared for low or zero-carbohydrate food. In circumstances where auser also uses an insulin pump, the dynamic glucose level alarm may alsobe used to detect pump failure as the dynamic glucose level alarm isbased on the actual rate of change of the user's glucose. Thus, thealarm can provide users with an early warning of a potentialhyperglycemic state.

In certain embodiments, alert conditions, such as those described above,may be triggered if a predetermined number of data points spanning apredetermined amount of time meet or exceed a threshold value. Inanother embodiment, an alarm may be output only when the data pointsspanning a predetermined amount of time have an average value whichmeets or exceeds the threshold value. Each condition that triggers analert may have different alert activation criteria. Additionally, thealert activation criteria may change depending on current conditions.

In certain embodiments, an alert condition can relate to the status ofone or more hardware components of the analyte monitoring device 200.For example, when a battery of the analyte monitoring device 200 dropsbelow a predetermined threshold voltage level or when a battery isreaching its expected life, an alert condition may be output.Additionally, an alert condition may relate to the status of signaltransmission, data processing and other processes of the device. Forexample, for signal transmission between the transmitter unit 102(FIG. 1) and the primary receiver unit 104 (FIG. 1), an alert conditionmay be detected by a processor of the receiver unit 104 if the receiverunit 104 does not receive a predetermined number of data packets insuccession or within a predetermined amount of time. In one aspect, thewireless connection icon 330 may show a disconnected status if thereceiver unit 104 does not receive a predetermined number of datapackets in succession or if packets are not received for a predeterminedamount of time (e.g. 2 minutes).

FIGS. 25A-25G describe various embodiments relating to the suppressionof alarms based on alert conditions according to embodiments of thepresent disclosure. As described above, a receiver, such as analytemonitoring device 200 (FIG. 2) is configured to enable a suppression ofoutputting an additional alarm associated with a detected alertcondition for a predetermined period of time after the alarm associatedwith the alert condition has been output.

Referring to FIG. 25A, a time dependent curve 2501 represents an analytelevel being monitored with a predetermined analyte level threshold forhypoglycemia being represented by the line 2502. When the analyte levelcurve 2501 moves from above the threshold 2502 to below the threshold(designated by point Tc) an alert condition is detected regarding theevent. In certain embodiments, the alert can be terminated within apredetermined amount of time (e.g., 60 seconds) or after the userdeactivates the alarm. However, as the curve 2501 fluctuates along thethreshold level for an extended period of time due to either noise ortrue signal variation, the alert condition may be detected multipletimes. As a result, an alarm associated with the alert condition may beoutput multiple times.

To alleviate this problem, outputting of the alarm is suppressed for apredetermined period of time (indicated by line tb). The predeterminedperiod of time starts when the occurrence of the alert condition isfirst detected (at point Tc). In certain embodiments, the predeterminedperiod of time represented by tb can be selected by a user to be 15minutes, 30 minutes or some other timeframe. Once the selected blockperiod of time expires, data corresponding to the current analyte levelof the user is received and evaluated by a processor of the analytemonitoring device 200 to determine whether a further alarm needs to beoutput. If it is determined that another alarm needs to be output (e.g.the alert condition still exists), the alarm is output. After the alarmis output, an additional time period can be defined and the processrepeats.

In accordance with this embodiment, a method 2500 for managing an alarmis provided as shown in FIG. 25B in which an alarm is output upon anoccurrence of an alert condition (2503). Once the alarm has been outputand subsequently silenced by a user (e.g. by the user actuating asoftkey button to mute the alarm or enter a snooze mode), outputtingadditional alarms associated with the condition are suppressed for apredetermined amount of time (2504). As will be appreciated by those ofordinary skill in the art, the predetermined period of time can besimilarly applied for alarms associated with other alarm conditions suchas, for example, low battery level, data transmission errors and thelike.

FIG. 25C illustrates an embodiment in which the analyte monitoringdevice 200 (FIG. 2A) may be configured to set or obtain a second analytelevel threshold within (e.g., above or below) the first threshold by apredetermined value. As shown in FIG. 25C, a time dependent curve 2511represents the analyte level being monitored with a predeterminedanalyte level threshold 2512. When the analyte level curve 2511 movesfrom above the threshold 2512 to below the threshold 2512 at point Tc,the alert condition (e.g., hypoglycemia) is detected. To reduce thefrequency at which the alarm is output, another predetermined threshold2513 can be established within the threshold 2512 by a predeterminedquantity represented by z. In certain embodiments, the quantity z can beselected based on the condition being monitored and/or based on userpreference. For example, for a hypoglycemia alarm, the quantity z can beselected as 10 mg/dL. Thus, if the hypoglycemia alarm is set at 60mg/dL, the second threshold level is 70 mg/dL. The analyte monitoringdevice 200 may be configured to suppress outputting of further alertnotifications until the analyte level passes within the second threshold2513 (as indicated by point Te). In this manner, the time period tdduring which the alert condition is suppressed depends on the distance zbetween the two thresholds 2512 and 2513 as well as the progression ofthe monitored analyte level over the time period.

FIG. 25D illustrates a method 2510 for managing an alarm as wasdescribed above with respect to FIG. 25C. The method 2510 includesoutputting an alert based on an occurrence of an alert condition (2514).After outputting the alert, a second analyte level threshold isestablished within the predetermined analyte level threshold (2515).Thereafter, alarms associated with the condition are suppressed untilthe analyte level exceeds the second threshold level (2516). In certainembodiments, the second analyte level threshold can be establishedbefore an alert condition is detected. The second analyte levelthreshold can be established by a user or healthcare professionalpreprogramming the various threshold levels into the analyte monitoringdevice 200.

FIG. 25E illustrates suppression of outputting an alarm associated withan alert condition for a predetermined amount of time. As shown in FIG.25E, time dependent curve 2521 represents an analyte level beingmonitored with respect to the predetermined analyte level threshold2522. When the analyte level curve 2521 moves from above the threshold2522 to below the threshold 2522, the alert condition is detected(represented as point Tc) and an alarm is output. The analyte monitoringdevice 200 may be configured to suppress outputting the alarm upon thefirst occurrence of the alert condition and additionally apply apredetermined wait period indicated by the line tp1. A processor of theanalyte monitoring device 200 suppresses outputting of the alarmcorresponding to the alert condition for the entire block periodrepresented by the line tp1. In certain embodiments, the wait period maybe selected by a user or healthcare professional. Upon expiration of thetime period, represented by point Ta, the alarm is output if thedetected alert condition still exists.

FIG. 25F illustrates a method 2520 for suppressing an alarm associatedwith an alert condition for a predetermined amount of time according toembodiments of the present disclosure. The method 2520 begins when analert condition is detected and an associated alarm is output by theanalyte monitoring device 200 (2523). Once the alarm has been output bythe analyte monitoring device 200, the processor of the analytemonitoring device 200 suppresses further alarms until the alertcondition persists for a predetermined amount of time (2524). When thealert condition has persisted for the predetermined amount of time, theprocessor determines whether the condition still exists. If it isdetermined that the condition still exits, the alarm is output (2525).

It is also contemplated that the analyte monitoring device 200 may beconfigured to enable suppression of an alarm associated with thedetected alert condition until an absence of the alert conditionpersists for a predetermined amount of time. Referring back to FIG. 25Eand as shown on the graph, after an alert condition is detected and analarm is output (represented by point Ta), the analyte level movesupward and exceeds the threshold 2522 at point Tac. After exceeding thethreshold 2522, the analyte level stays above the threshold 2522 anddoes not return back below the threshold level. In such cases, theanalyte monitoring device 200 may be configured to enable suppression ofoutputting a further alarm until an absence of the condition (whichstarts from point Tac) persists for a predetermined period of time(represented by the line tp2). Thus, the alarm will only be suppressedafter the condition that initially triggered the alarm has not beendetected for the entire predetermined amount of time represented by theline ts. In certain embodiments, the time period represented by the linetp2 can be selected based on user input, such as, for example, 3minutes, 5 minutes 10 minutes, etc.

FIG. 25G illustrates a method 2530 for suppressing outputting of analarm associated with a condition until an absence of the conditionpersists for a predetermined amount of time according to embodiments ofthe present disclosure. Method 2530 begins when an alarm is output inresponse to the detection of an alert condition (2531). In certainembodiments, the processor issues a command to suppress furtheroutputting of an alarm corresponding to the detected alert conditionuntil an absence of the alert condition persists for a predeterminedperiod of time since the first occurrence of an absence of the alertcondition (2532). If the alert condition is not detected in thatpredetermined time period, the alarm will not be output by the analytemonitoring device 200.

Additionally, although specific examples were used above with respect tohypoglycemia, it is contemplated that the alarm suppression techniquesmay be used with all detected alert conditions, such as, for example,hyperglycemia, impending hypoglycemia and impending hyperglycemia aswell as alarms relating to one or more parameters corresponding to theoperation of the analyte monitoring device 200.

FIG. 26 illustrates an exemplary flow of a plurality of user interfacescreens corresponding to establishing a connection between a sensor,such as for example, sensor 101 (FIG. 1) and a receiver unit, such as,for example receiver unit 104 (FIG. 1) according to embodiments of thepresent disclosure. In certain embodiments, the user may select “Connectto Sensor” from the sensor submenu 700 (FIG. 7), and begin the processof establishing a data link to the sensor and transmitter (5310). Theuser interface provides a find sensor screen which includes theinstructions “Hold Companion Next to Sensor. Looking for sensor . . . .” The receiver then waits for a response packet from the transmitter(5320), such as, for example, transmitter unit 102 (FIG. 1). If aresponse packet is not received, a “Transmitter Not Found” screen andfailure tone (5330) are output from the receiver. In certainembodiments, the “Transmitter Not Found” screen is a yellow messagescreen that asks the user to make sure the transmitter is attached to asensor mount, and asks the user if the user wants to try again to locatethe transmitter.

If a response packet is received at the receiver, and an unsupportedtransmitter is detected (5360), an “Unsupported Transmitter” screen isoutput on the display of the receiver and the receiver outputs a failuretone (5370). If a response packet is received at the receiver and anunknown transmitter is detected (5380) and the sensor life is active(5390), an “Unknown Transmitter” display screen is output on the displayof the receiver and the receiver outputs a failure tone (5400). Incertain embodiments, the “Unknown Transmitter” display screen is ayellow message screen and notifies the user that the detectedtransmitter is not the user's transmitter. The user may also be promptedvia a display screen as to whether they would like to use the detectedsensor and transmitter.

If an unknown transmitter is detected and the sensor life is inactive(5390), a “New Transmitter Found” display screen is output on thedisplay of the receiver and the receiver outputs a success tone (5410).The display screen of the receiver outputs the following statement: “NewTransmitter Found: Is this yours?” The display screen also displays atransmitter identification number that may be used to determine whetherthe identified transmitter matches the identification number of thetransmitter the user is actually using. The transmitter identificationnumber may be represented as letters only, numbers only, or alphanumerictext.

If a known transmitter is detected (5380) and a sensor count number hasincremented (5420), a “Sensor Code” editable screen is output on thedisplay of the receiver, and a success tone is output (5340). At the“Sensor Code” display screen, the user is prompted to “Enter sensor codeto start sensor.” An editable field “Sensor Code=” is provided on thedisplay of the receiver to enable the user to enter the sensor code. Ifthe sensor life is inactive (5500), a “Sensor Not Started” screen (5520)is output on the display of the receiver and the user is asked whetherthe user wishes to try to connect to the sensor again.

If the sensor life is active (5500), a new transmitter was not detected(5510), the sensor counter has incremented, and the user chooses“Cancel” at the “Sensor Code” screen, a “Suggest Replace Sensor Due toExpiration” message is output on the display of the receiver (5470). Incertain embodiments, the user interface displays a “Sensor Expired”message because the receiver is uncertain about what sensor life thereceiver is tracking. If the sensor life is active (5500) and a newtransmitter was detected (5510) but the user chooses to Cancel at the“Sensor Code” screen, the sensor menu is output on the display of thereceiver (5300).

If a known transmitter is detected (5380) and the Sensor Count numberhas not incremented (5420), the “Home” screen is output on the displayof the receiver and the receiver outputs a success tone (5350). If aknown transmitter is detected (5380), and the sensor life is inactive,and the Sensor Count number has not incremented (5420), a yellow alertscreen is output on the display of the receiver with message reading“Suggest Replace Sensor Due to Expiration” and the receiver outputs anintermediate level alert (5470). If a known transmitter is detected(5380) and the RF radio is off (5480), a “Radio Off” display screen isoutput on the display of the receiver (5490).

In addition to the “Connect to Sensor” menu screen item, the user mayselect a “Calibration BG”, which provides a “Calibration BG” messagescreen type, The message screen asks the user “Do you want tocalibrate?” and offers the user the option to respond. A message screendisplaying the time period in which the next calibration is needed alongwith a grace period may be output on the display of the receiver.

In certain embodiments described herein, an analyte monitoring deviceincludes a user interface with a display and a plurality of actuators.The display is configured to output a plurality of display screens,including a home screen divided into a plurality of simultaneouslydisplayed panels. The plurality of displayed panels may include displaysof various indicators including rate of change of analyte levels,current analyte levels, analyte trend indicators, and statusinformation, such as battery life and calibration status. The pluralityof actuators, in certain embodiments, may be utilized to adjust andchange the various available displays of the analyte monitoring device.

In one aspect, an analyte monitoring device may include a user interfacehaving a display and a plurality of actuators, wherein the display isconfigured to render a plurality of display screens, including at leasta home screen and an alert screen, wherein the home screen is dividedinto a plurality of simultaneously displayed panels, wherein a firstpanel of the plurality of panels is configured to display a rate ofchange of continuously monitored analyte levels in interstitial fluid,wherein a second panel of the plurality of panels is configured tosimultaneously display a current analyte level and an analyte trendindicator, and wherein a third panel of the plurality of panels isconfigured to display status information of a plurality of components ofthe analyte monitoring device, and when an alarm condition is detected,the display is configured to render the alert screen in place of thehome screen, the alert screen having information corresponding to thedetected alarm condition, and wherein at least one of the plurality ofactuators is configured to affect a further output of the analytemonitoring device corresponding to the detected condition.

In one embodiment, the first panel may include a timeline graph having aplurality of indicators disposed thereon, wherein each of the pluralityof indicators represent an event.

In a further embodiment, an event may be selected from a group of eventsconsisting of a discrete blood glucose measurement, an insulin dose, anexercise period, a meal, a state of health, and a custom event.

In another embodiment, information displayed in at least one theplurality of panels may be color coded based on a severity of acondition the information represents.

In one embodiment, at least one of the actuators may be programmable bya user.

In another embodiment, the display may be rendered in an orientationbased on a type of alert screen displayed.

In another embodiment, at least one of the plurality of panels may beexpandable when at least one of the plurality of actuators is actuated.

Another aspect of the present disclosure may include receivingcontinuous analyte level information data from a transmitter, thetransmitter having a sensor in fluid contact with interstitial fluid,displaying a graphical representation of a rate of change of thecontinuous analyte level data over a predetermined amount of time in afirst panel of a display screen of the display device, simultaneouslydisplaying a numerical representation of a current analyte level and aniconic trend indicator in a second panel of the display screen of thedisplay device, wherein the current analyte level is compared with aplurality of subsequent analyte levels, and wherein the current analytelevel and the trend indicator are updated only when a difference betweenthe plurality of subsequent analyte levels and the current analyte levelexceeds a predetermined threshold, displaying an alert screen inresponse to a detected condition, wherein the alert screen is displayedin place of the first panel and the second panel, and controllingfurther output of the display device based on user actuation of at leastone of a plurality of buttons disposed on the display device when thealert screen is displayed.

In one embodiment, the alert screen may be displayed in a third panel,wherein the third panel is displayed simultaneously with the first paneland the second panel.

In another embodiment, the graphical representation may include at leastone event icon corresponding to a user event.

In a further embodiment, the user event may correspond to the detectedcondition.

In one embodiment, the graphical representation may include a first userdefined analyte level threshold indicator and a second user definedanalyte level threshold indicator, wherein when the current analytelevel information passes at least one of the first analyte levelthreshold indicator or the second analyte level threshold indicator, ananalyte level alert is displayed.

A further embodiment may include displaying a plurality of iconic statusrepresentations of a plurality of components of the display device,wherein the plurality of iconic status representations are displayed ona third panel of the display screen of the display device, wherein thethird panel is simultaneously displayed with the first panel and thesecond panel.

Another embodiment may include automatically rotating the displayedalert screen into a predetermined orientation based on a type ofdetected condition.

Yet another embodiment may include displaying a menu screen on a thirdpanel of the display screen of the display device, wherein the thirdpanel is simultaneously displayed with the first panel and the secondpanel.

Another aspect of the present disclosure may include an analytemonitoring device having a user interface, wherein the user interfacemay include a display, wherein the display is configured tosimultaneously display a plurality of distinct panels, wherein a firstpanel of the plurality of distinct panels displays historical analytelevel information over a predetermined amount of time, and wherein asecond panel of the plurality of distinct panels displays real-timeanalyte level information, and displays an alert screen in response toan alert condition being detected, wherein the alert screen is displayedin place of the plurality of distinct panels when the alert condition isdetected, and a plurality of buttons, wherein at least one of theplurality of buttons is configured to interact with at least one of theplurality of panels when the plurality of panels are displayed andwherein at least the one of the plurality of buttons is configured tointeract with the alert screen when the alert screen is displayed.

In one embodiment, actuation of the at least one of the plurality ofbuttons may be configured to affect an output of the analyte monitoringdevice when the alert screen is displayed.

In another embodiment, the output of the monitoring device may compriseat least one of a display output, an audible output, a vibratory output,and a combination thereof.

In one embodiment, the detected alert condition may correspond to one ofa low urgency alert condition, an intermediate urgency alert condition,a medium urgency alert condition, and high urgency alert condition.

In another embodiment, the alert screen may be displayed in a rotatedposition based on a type of condition the alert screen represents.

In one aspect of the present disclosure a user interface for a personalmedical device may include a display configured to display a home screenhaving a first section configured to display color coded graphicalinformation corresponding to historic analyte levels of a user and asecond section configured to simultaneously display color coded textualinformation corresponding to current analyte levels of the user, and aplurality of alert screens, wherein the plurality of alert screens arehierarchically arranged based on a severity of a condition that each ofthe plurality of alert screens represent, and a plurality of buttons,wherein the plurality of buttons have a first functionality when thehome screen is displayed and wherein the plurality of buttons have asecond functionality when each of the plurality of alert screens aredisplayed.

In one embodiment, a size of the first section of the home page may beadjustable with respect to a size of the second section of the homepage.

In another embodiment, a position of the first section of the home pagemay be adjustable with respect to a position of the second section ofthe home page.

In another embodiment, one of the plurality of alert screens may bedisplayed in a third section of the home screen, wherein the thirdsection of the home screen is simultaneously displayed with the firstsection of the home screen and the second section of the home screen.

In one embodiment, when the third section of the home screen isdisplayed, a size of the first section of the home screen and a size ofthe second section of the home screen may be automatically adjusted.

In one embodiment, the display may be a self-orientating display.

In another embodiment, the orientation of the display may beautomatically adjusted based on one of the plurality of alert screensdisplayed.

One embodiment may further include a third section, wherein the thirdsection of the home screen displays a plurality of icons representingrespective components of the personal medical device, and wherein thethird section is simultaneously displayed with the first section of thehome screen and the second section of the home screen.

In one embodiment, when at least one alarm screen is displayed, it maybe displayed in at least one of the first section of the home screen,the second section of the home screen or the third section of the homescreen.

In one embodiment, a first alert screen having a first hierarchicalorder may be displayed in one of the first section of the home screen orthe second section of the home screen, and wherein a second alert screenhaving a second hierarchical order is displayed in the other of thefirst section of the home screen or the second section of the homescreen.

Another aspect of the present disclosure may include receiving aplurality of analyte levels including a most recent analyte level and atleast one historical analyte level, defining a plurality of thresholdvalues with respect to the most recent analyte level, retrospectivelycomparing the at least one historical analyte level to at least one ofthe plurality of threshold values to determine whether the at least onehistorical analyte level exceeds the at least one of the plurality ofthreshold values, and outputting an alert notification when the at leastone historical analyte level exceeds the at least one of the pluralityof threshold values.

A further embodiment may include determining whether the at least onehistorical analyte level was received within a predetermined window andretrospectively comparing the at least one historical analyte level tothe at least one of the plurality of threshold values when it isdetermined that the at least one historic analyte level was receivedwithin the predetermined window.

In one embodiment, the predetermined window may be defined by a minimumtime duration with respect to the most recent analyte level and amaximum time duration with respect to the most recent analyte levelinformation.

In another embodiment, the at least one of the plurality of thresholdvalues may correspond to a maximum rate of change of the historicalanalyte value over a predetermined time period.

In another aspect, an apparatus may include one or more processors, anda memory for storing instructions for access by the one or moreprocessors which when executed, receives a plurality of analyte levelsincluding a most recent analyte level and at least one historicalanalyte level, defines a plurality of threshold values with respect tothe most recent analyte level, retrospectively compares the at least onehistorical analyte level to at least one of the plurality of thresholdvalues to determine whether the at least one historical analyte levelexceeds the at least one of the plurality of threshold values, andoutputs an alert notification when the at least one historical analytelevel exceeds the at least one of the plurality of threshold values

In one embodiment, the memory for storing instructions for access by theone or more processors, which when executed, may determine whether theat least one historical analyte level was received within apredetermined window and retrospectively compares the at least onehistorical analyte level to the at least one of the plurality ofthreshold values when it is determined that the at least one historicanalyte level was received within the predetermined window.

In one embodiment, the predetermined window may be defined by a minimumtime duration with respect to the most recent analyte level and amaximum time duration with respect to the most recent analyte levelinformation.

In another embodiment, the at least one of the plurality of thresholdvalues may correspond to a maximum rate of change of the historicalanalyte value over a predetermined time period.

In one embodiment, at least one of the actuators may be illuminated by alighting assembly.

In one embodiment, the lighting assembly may include a light source anda light pipe, wherein the light pipe is configured to direct light fromthe light source to the at least one of the actuators.

One embodiment may include a test strip port.

In another embodiment, at least a portion of the test strip port may beilluminated by an illumination assembly.

In another embodiment, the illumination assembly may include a lightsource and light pipe, and wherein at least a portion of the test stripport comprises the light pipe.

In another aspect of the present disclosure, an analyte monitoringdevice may include a housing, a display disposed in the housing, whereinthe display is configured to output a plurality of distinct displayareas, wherein at least one of the distinct display areas is configuredto output data corresponding measured analyte levels received from atranscutaneously positioned sensor and at least a second one of thedistinct display areas is configured to output data corresponding to theanalyte monitoring device, a plurality of actuators disposed in thehousing wherein at least one of the plurality of actuators is configuredto interact with at least one of the distinct display areas, and anillumination assembly disposed in the housing, wherein the illuminationassembly is configured to transfer light from a first area of thehousing to a second area of the housing.

In one embodiment, the illumination assembly may include at least onelight source and at least one light pipe.

Another embodiment may include a test strip port configured to receive atest strip.

In one embodiment, the illumination assembly may be configured toilluminate at least a portion of the test strip port.

In another embodiment, at least a portion of the test strip port maycomprise at least a portion of the illumination assembly.

In another embodiment, the illumination assembly may be automaticallyactivated in response to a test strip being inserted into the test stripport.

In one embodiment, the illumination assembly may be configured tosimultaneously direct light to the first area of the housing and secondarea of the housing.

Various other modifications and alterations in the structure and methodof operation of this disclosure will be apparent to those skilled in theart without departing from the scope and spirit of the embodiments ofthe present disclosure. Although the present disclosure has beendescribed in connection with particular embodiments, it should beunderstood that the present disclosure as claimed should not be undulylimited to such particular embodiments. It is intended that thefollowing claims define the scope of the present disclosure and thatstructures and methods within the scope of these claims and theirequivalents be covered thereby.

What is claimed is:
 1. An analyte monitoring device, comprising: a userinterface having a display, the display configured to render a pluralityof display screens including a plurality of panels including a firstpanel configured to display a rate of change of monitored analytelevels, a second panel configured to display a current analyte level oran analyte trend indicator or both the current analyte level and theanalyte trend indicator simultaneously, and a third panel configured todisplay status information of the analyte monitoring device; whereinwhen an alarm condition is detected, the display is configured toreplace one of the plurality of panels with an alert screen havinginformation corresponding to the detected alarm condition.
 2. Theanalyte monitoring device of claim 1, wherein the first panel, thesecond panel and the third panel are simultaneously displayed on theuser interface.
 3. The analyte monitoring device of claim 1, wherein theuser interface is configured to affect a further output of the analytemonitoring device corresponding to the detected alarm condition.
 4. Theanalyte monitoring device of claim 1, wherein the first panel includes atimeline graph having a plurality of indicators, wherein each of theplurality of indicators represents an event.
 5. The analyte monitoringdevice of claim 4, wherein the event is selected from a group of eventsincluding a discrete blood glucose measurement, an insulin dose, anexercise period, a meal, a state of health, or a custom event.
 6. Theanalyte monitoring device of claim 1, wherein the information displayedon one of the panels is color coded based on a severity of a conditionthe information represents.
 7. The analyte monitoring device of claim 1,wherein the display is rendered in an orientation based on a type ofalert screen displayed.
 8. The analyte monitoring device of claim 1,wherein at least one of the plurality of panels is expandable when theuser interface is actuated.
 9. A method, comprising: displaying agraphical representation of a rate of change of monitored analyte leveldata in a first panel of a display screen of a display device;simultaneously displaying a numerical representation of a currentanalyte level and a trend indicator in a second panel of the displayscreen of the display device, wherein the current analyte level and thetrend indicator are updated when the current analyte level exceeds apredetermined threshold; and displaying an alert screen in response to adetected condition, wherein the alert screen is displayed in place ofthe first panel or the second panel.
 10. The method of claim 9, furtherincluding controlling output of the display device based on useractuation of at least one of a plurality of buttons disposed on thedisplay device when the alert screen is displayed.
 11. The method ofclaim 9, wherein the graphical representation includes at least oneevent icon corresponding to a user event.
 12. The method of claim 11,wherein the user event corresponds to the detected condition.
 13. Themethod of claim 9, wherein the graphical representation includes a firstuser defined analyte level threshold indicator and a second user definedanalyte level threshold indicator, wherein when the current analytelevel passes at least one of the first user defined analyte levelthreshold indicator or the second user defined analyte level thresholdindicator, an alert is displayed.
 14. The method of claim 9, furthercomprising displaying one or more status representations of one or morecomponents of the display device, wherein the one or more statusrepresentations are displayed on a third panel of the display screen ofthe display device, and further wherein the third panel issimultaneously displayed with the first panel and the second panel. 15.The method of claim 9, further comprising automatically rotating thedisplayed alert screen into a predetermined orientation based on thedetected condition.
 16. The method of claim 9, further comprisingdisplaying a menu screen on a third panel of the display screen of thedisplay device, wherein the third panel is simultaneously displayed withthe first panel and the second panel.
 17. A user interface device,comprising: a display, wherein the display is configured to:simultaneously display a plurality of panels including a first paneldisplaying historical analyte level information, and a second paneldisplaying current analyte level information; and display an alertscreen in place of one or more of the plurality of panels in response toa detected alert condition; and a plurality of input componentsincluding at least one input component configured to interact with thealert screen when the alert screen is displayed.
 18. The user interfacedevice of claim 17, wherein the at least one of the plurality of inputcomponents is configured to interact with at least one of the pluralityof panels when the plurality of panels are displayed.
 19. The userinterface device of claim 17, wherein actuation of the at least one ofthe plurality of input components is configured to affect an output ofan analyte monitoring device when the alert screen is displayed.
 20. Theuser interface device of claim 19, wherein the output of the analytemonitoring device comprises at least one of a display output, an audibleoutput, a vibratory output, or one or more combinations thereof.
 21. Theuser interface device of claim 17, wherein the detected alert conditionincludes one of a low urgency alert condition, an intermediate urgencyalert condition, a medium urgency alert condition, or a high urgencyalert condition.
 22. The user interface device of claim 17, wherein thealert screen is displayed in a rotated position based on an alert screenrepresentation.
 23. The user interface device of claim 17, wherein thedisplay is a self-orientating display.